Uberfire is now AppFormer, and is inside KIE group

[Christopher-Chianelli]

Link to maintained repo: https://github.com/kiegroup/appformer

RedHatOfficial.github.io/app/data/projects.json

Lines 178 to 184 in 10cefd7

	{
	"projectName": "UberFire",
	"projectDescription": "A web framework for a superior experience in building extensible workbenches and console type applications",
	"projectRepository": "https://github.com/AppFormer/uberfire",
	"projectWebsite": "http://uberfireframework.org",
	"category": "Development"
	},

[bproffitt]

@Christopher-Chianelli So, should I just drop it in favor of KIE like I did initially with the other formerly separate projects?

[Christopher-Chianelli]

@bproffitt Depends on how granular you want the list to be. If you include AppFormer directly, then you should also include the rest of KIE group projects (AppFormer, Drools, OptaPlanner, etc.) as separate entries. If you do include it, it might be worth separating the data into two lists: Teams and Projects, and have Projects point to their team (so add a field, "team" to the Projects dataset whose value need to be exactly the same as the "teamName" of the corresponding team in the Teams dataset).

[bproffitt]

@Christopher-Chianelli To be honest, I would like to just focus on the top-level projects, if we could. I don't want to start listing sub-projects if we can help it (like moVirt in oVirt-land). For consistency's sake, let's drop Uberfire until we can figure out a way to list sub-projects.

[Christopher-Chianelli]

@bproffitt Probably should add that to the README.md, so contributors know they should not add sub-projects.

[bproffitt]

Updated README and pulled UberFire out in #129 . Closing, with thanks!