[D8] szentiras.hu Reference Formatter

Fixed the git clone URL in the issue summary for non-maintainer users.

We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)

Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).

I'm a robot and this is an automated message from Project Applications Scraper.

Hi @Bubu.

Invited to help a bit with the Review Process and the queue here are some remarks, the first and most important: I'm not the person to decide on that but the review process implicates that your code should be long enough to analyze coding skills and should not only consist of a few copied and adapted routines. This does not mean that your project isn't worth being published. You can always contact an administrator to publish the project in the project name space.

The goal of this application review process is to determine if your code allows to evaluate knowledge and skills and if the answer is yes to promote not only your project but you as a user.

Based on this introduction: Probably it would be a good idea to move both projects out of the sandbox, the [D7] and the [D8] version and to merge them into one project that you can maintain. Please see https://www.drupal.org/node/2505727

Manual Review

Individual user account

Yes: Follows the guidelines for individual user accounts.

No duplication

Yes: Does not cause module duplication and/or fragmentation.

Master Branch

Yes: Follows the guidelines for master branch.

Licensing

Yes: Follows the licensing requirements.

3rd party assets/code

Yes: Follows the guidelines for 3rd party assets/code.

README.txt/README.md

Yes: Follows the guidelines for in-project documentation and/or the README Template.

Code long/complex enough for review

No: Does not follow the guidelines for project length and complexity.

Secure code

Yes: Meets the security requirements. / No: List of security issues identified.

Coding style & Drupal API usage

List of identified issues in no particular order. Use (*) and (+) to indicate an issue importance. Replace the text below by the issues themselves:

1. * As I pointed out above, your code is probably not long enough to promote your account. Please consider asking for a single project promotion.

The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.

If added, please don't remove the security tag, we keep that for statistics and to show examples of security problems.

This review uses the Project Application Review Template.

Regards.
uh

Hi @bubu.

I've reviewed your reviews as well and at least two of the three reviews contain nothing more than findings of the automatic review process using pareview.sh. And this means that you're not qualifying for the review bonus.

Regards.
uh

Hi @bubu.

If a single project promotion is ok for you, git administrators should be notified by the issue tag.

Regards.
uh

Hi @bubu.

I changed it to needs review.

uli

Thank you for your contribution!

After 2017 March 7 everyone can promote a project to a full project.  A full project has a short project name and a drupal.org/project URL.  It can also have releases (like alpha1 or 1.0).  Edit your sandbox project, and then choose the 'Promote' tab.

https://www.drupal.org/docs/8/understanding-drupal-version-numbers/drupa...
https://www.drupal.org/docs/8/choosing-a-drupal-version/what-do-version-...
https://www.drupal.org/docs/8/understanding-drupal-version-numbers/what-...
https://www.drupal.org/docs/8/choosing-a-drupal-version/release-stable-v...

If you'd like to opt into security coverage, please ensure your module is ready for a full release, and then set this issue back to 'needs review'

Immense apologies for how long it took to get to this review completed.

I am closing due to lack of replies.

If you are still working on this application, and you need to be able to opt in the security coverage for the projects you maintain, please set the status to Needs review. (See also the project application workflow).