I do not see that at all. I am using and contributing to lots of open source projects, and never had any problem with the fact that all of them use different tools. Having a handfull now using the same tool does not change anything. From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] On Behalf Of Richard Monson-Haefel Sent: Dienstag, 28. August 2018 20:10 To: Jakarta EE community discussions Subject: Re: [jakarta.ee-community] Kanban boards for GitHub issues Well, the reason I think its important to be consistent is not for the PMC and its not for the committers specifically, although they would benefit, its for the community at large. being independent is great but being transparent is far more important. Transparency works better when their is consistency. On Tue, Aug 28, 2018 at 1:03 PM, Ivar Grimstad <ivar.grimstad@xxxxxxxxx> wrote: I don't see the PMC would ever care about how the EE4J projects are managed internally. If the GitHub extensions require some sort of assistance/configuration by the Eclipse Foundation Webmaster, they may have something to say about it. Require is probably too strong of a word. I should have said, encourage. On Tue, Aug 28, 2018 at 12:45 PM, Markus KARG <markus@xxxxxxxxxxxxxxx> wrote: At least at JAX-RS we do not plan in such detail upfront, so we do not need any kind of kanban board at all. Also, projects are independent. So you cannot require us to use tools we do not need. -Markus Having a single system would, in my opinion, that can cascade hierarchically would be best. That way I can look at the entire project at the top level and drill down to individual projects. This would make everything both very transparent and easy to access. We already require all of the projects to use GitHub. I see no problem in requiring them all to use the same kanban board. If the new Projects feature on GitHub supports that then we should use that. On Tue, Aug 28, 2018 at 11:13 AM, Werner Keil <werner.keil@xxxxxxxxx> wrote: Hi, Which would allow to coordinate issues by multiple components and features across e.g. a Jakarta EE release. The same board is also available inside each project. A nice feature close to JIRA links is a "requires" tag allowing to define some issues as show-stoppers for others and vice versa. Any other similar tools you would recommend? While the top level project is probably something the Platform project may find useful, other tools and "Kanban" extensions are probably up to individual projects like using Travis-CI or other tools if they find them helpful to their goals. If there are other alternatives that projects already use, please let us know, otherwise it may be more for individual project lists to discuss what may be useful. _______________________________________________ jakarta.ee-community mailing list jakarta.ee-community@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________ jakarta.ee-community mailing list jakarta.ee-community@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________ jakarta.ee-community mailing list jakarta.ee-community@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community
-- Java Champion, JCP EC/EG Member, EE4J PMC, JUG Leader _______________________________________________ jakarta.ee-community mailing list jakarta.ee-community@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community
|