Hello John,
thanks for replying to the discussion! I think the most important
point is, that this topic gets a little bit of attention.
-----
I also do think that fragmentation is an issue, looking at Apache
projects it is sometimes really hard to understand where the
project related stuff is located (source control, bug tracking,
etc...)
But I also have to agree with Kai, the split is already been made
by allowing GitHub hosted projects. And now the
split/fragmentation is not only between projects, but also inside
a project. Source code "here", issues "there". Which is harder to
explain than to explain "this project does it this way, the other
in another way".
Also with Eclipse projects, I sometimes find it hard to locate the
relevant entry points looking at each projects home page. And
Eclipse SCADA is no difference ;-)
Although I guess this far exceeds the "IoT" space, it think one
possible solution would be:
1) Create a simple "fact sheet" for each project containing Bug
Tracker, Source Control, Downloads
2) Require all project home pages to include a well defined
badge/button to link to this fact sheet (like the incubation logo)
I think that the "fact sheet" already is available, although in
too much detail, in the project overview screen [1]. I guess it is
not much more than simply streamlining the layout so that all
information can be put on one screen. Remove all the project
descriptive texts and you are good to go. Think of it as a page
were people which already know the project can look at to get in
deeper (as a transition from user to contributor).
The second point is a simple requirement to let people actually
find this page. Right now the project pages are filled with data
and I guess most people (users) are not aware these pages exist.
-----
I have to admit, as soon as you allow one other system, everybody
else will want a different system as well. Jira, Trac .. you name
it. Personally I think this it is not a good idea to allow them
all. But if you decided to allow GitHub for source control, then
there is should also be the choice to go with the GitHub issue
tracker. Otherwise the move to allow GitHub was wrong in the first
place.
-----
In the end I think it is brings more benefit for each Eclipse
project allowing for a consistent project view than to have a
global view an all Eclipse projects. Most people working on
Eclipse SCADA will never care about bugs in CDT for example.
Sometimes this will raise a barrier between Eclipse projects,
because easy referencing is not possible. But then maybe each
project should decide what is more worth for them.
If the decision is that the global "non-fragmentation" is if more
worth to the Eclipse Foundation, I fully understand this as well.
But this would mean that projects should not be hosted on GitHub
any longer. Which I personally would find ok.
-----
I am sorry I came up with that much text ;-)
Jens
[1]
https://projects.eclipse.org/projects/technology.eclipsescada
On 06/18/2015 03:54 AM, John Arthorne wrote: