-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mention Drools, OptaPlanner and jBPM (not just KIE) #145
Comments
Yeah, I am unsure how to handle this. All the public-facing content makes a strong point to refer to KIE, which is why it was consolidated here. Plus, for now we're trying to only list top-level projects, so another reason to highlight KIE. |
FWIW, I've updated ticket with suggested name, website url and repo url's. On Red Hat developer's projects page, they are mentioned separately. |
Proposed change to resolve RedHatOfficial#145 Additionally considering: > ---------- Forwarded message ---------- > Date: Thu, Mar 29, 2018 at 12:03 PM > ... > The criteria for listing is any project *and* sub-project that you work on as part of your job at Red Hat. Thanks, MM
Hi @bproffitt As @ge0ffrey highlighted Drools, OptaPlanner and jBPM are separate projects:
I believe on this landing page instead we are giving semantics to a GitHub organization for a project/subproject structure, which doesn't necessarily apply to all projects and especially to Kie as it's only used for the pragmatical organisation of tying the projects together (as they have affinity, but indeed separate projects). Based on the above, I understand there will be a research to better accomodate other types of GitHub setups (#150) but meanwhile for all the reasons explained for Drools, OptaPlanner and jBPM can we kindly merge #149 please? Thank you in advance for your feedback |
Red Hat sponsors drools.org, optaplanner.org and jbpm.org.
On GitHub, they are all in the GitHub organization kiegroup, which probably explains why they aren't mentioned individually, but they should.
The text was updated successfully, but these errors were encountered: