Hi Greg and the great team of Jetty,

I have not yet done any contributions to Jetty project but I would very
much like to start.
So as a potential contributor, I have the following observations as I
wanted to start.

I am sure there has been a reason but I do not see the code formatter and
coding templates in the main repo[1].
And, by formatter and coding templates, I mean [2] and [3] which seem to be
living still under a different repo tree.
But both are described and documented at [4].
I am aware that there're arguments for and against having the supporting
material for contributors in the repo or not,
but I am still more convinced having them as part of the repo brings the
advantage of creating history for them as well.
This can be even on a separate repo. Maybe this could be another "Help
Wanted" issue at GitHub?

Then, by any chance, is there a plan to unify Jetty documentation and its
code?
This will bring another advantage that when a PR is sent, maybe part of its
review process will be also
to verify the documentation part of the changes?

Regards,
Behrooz


[1]: https://github.com/eclipse/jetty.project/blob/master/CONTRIBUTING.md
[2]:
http://git.eclipse.org/c/jetty/org.eclipse.jetty.admin.git/tree/jetty-eclipse-java-format.xml
[3]:
http://git.eclipse.org/c/jetty/org.eclipse.jetty.admin.git/tree/jetty-eclipse-codetemplates.xml
[4]:
https://www.eclipse.org/jetty/documentation/current/advanced-contributing.html


On Wed, Mar 2, 2016 at 7:59 PM, Greg Wilkins <[email protected]> wrote:

> All,
>
> The Jetty project has recently completed our move to Github for our master
> repository <https://github.com/eclipse/jetty.project> and issue tracking
> <https://github.com/eclipse/jetty.project/issues>.  Jetty is still an Eclipse
> Foundation <https://www.eclipse.org/jetty/> project and our IP is audited
> by the eclipse processes, but the excellent collaboration tools available
> from GitHub are now fully available to assist with the development of the
> Jetty project. We have already seen an increase in community contributions
> <https://github.com/eclipse/jetty.project/pulls?utf8=%E2%9C%93&q=is%3Apr+>
> as a result!
>
> Another note is that Webtide <https://webtide.com/>, the company that
> develops jetty and provides commercial support, shifted to being 100% owned
> by the core Jetty committers
> <https://github.com/eclipse/jetty.project/graphs/contributors>, allowing
> us to retain our ongoing commitment of maintaining the Jetty project as a
> 100% open offering.
>
> I mention these two changes as I call your attention to the new "Help
> Wanted
> <https://github.com/eclipse/jetty.project/issues?q=is%3Aopen+is%3Aissue+label%3A%22Help+Wanted%22>"
> label in the Github Issues area for Jetty. Now why is a commercially
> supported open source project asking for help from the community?
>
> Not only are our commercial support clients the projects ultimate source
> of funding, they are our primary source of use-cases, examples and
> challenges that drive Jetty development and set our priorities.  However
> not every enhancement is going to be sponsored by a commercial client and
> neither is every user going to take up a commercial support contract.
>
> Short of taking up a commercial support contract, contributing to "Help
> Wanted
> <https://github.com/eclipse/jetty.project/issues?q=is%3Aopen+is%3Aissue+label%3A%22Help+Wanted%22>"
> issues is an ideal way to give back to the community and to help steer the
> future of the project.  Note also that help comes can come in many forms
> which includes testing, requirements, examples and documentation, so that
> showing interest and willing in a "Help Wanted
> <https://github.com/eclipse/jetty.project/issues?q=is%3Aopen+is%3Aissue+label%3A%22Help+Wanted%22>"
> issue may assist us in making it a priority for our own engineers to
> complete without commercial support.
>
> Finally, contributions to any open source project appear as great resume
> fodder and we ourselves are always on the lookout for talent, both from a
> project perspective and Webtide itself.
>
> Keep those PRs coming!
>
> --
> Greg Wilkins <[email protected]> CTO http://webtide.com
>
> _______________________________________________
> jetty-dev mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>



-- 
-- Behrooz Nobakht
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

Reply via email to