Community
Participate
Working Groups
The wiki is a bit messy and has a considerable amount of dead information on it. Here's a quick outline of what the structure could be like to make things a bit neater - we ca use the capability of the wiki to have hierarchical names to make things easier to navigate. Front Page -> contains about, download instructions, latest news and links Components IM SOAS SC... etc there is a page for each component. Planning -> general planning material for the project, agendas, minutes Developers -> getting a build done, checking things out, explanation of code layout etc Documents -> presentations, articles, tutorials, flash demos, etc Events -> conferences, initiatives, meetups, regular conference calls Cleaning up the site will cause peoples links that they have saved to break, so apologies in advance! The actual wiki names will look like: STP STP/Component STP/Planning STP/Developers STP/Documents STP/Events
I've started work on this, using some of the features borrowed from the Buckminster wiki and other elements to allow breadcrumb navigation. I've put together starting pages for all the components and they follow the schema STP/IM_Component STP/BPMN_Component etc, you can see the links at the components list at the bottom of http://wiki.eclipse.org/STP/TestPage The plan is to slowly bring over all of the links from the existing front page of the wiki, and then encourage component leads to garden their own particular areas :)
Some stp-dev activity, for the record: http://dev.eclipse.org/mhonarc/lists/stp-dev/msg01708.html
As part of the work for EclipseCon 2008, I have started working on our component page. I have added a particular category: BPMN that I will propagate to our pages.
Oisin, I guess you will need to update this page: http://wiki.eclipse.org/index.php/STP_Sub-project_specific_pages Do we need to add the STP category everywhere in our component pages? It seems using "subfolders" like STP/BPMN actually generates the STP/BPMN page. Would it be possible to move the component home pages to that address ? It would certainly help people to find their way around.
(In reply to comment #4) > Oisin, I guess you will need to update this page: > > http://wiki.eclipse.org/index.php/STP_Sub-project_specific_pages Yes, I'm going to take that page away completely, it is replaced by the Components section on the home page. I'll move all the content to the component specific pages. > Do we need to add the STP category everywhere in our component pages? This would be good. Categories are used for searching, and there is also a category 'index page' (eg http://wiki.eclipse.org/index.php?title=Category:SOA&action=edit) which can serve as a overview of all the pages. I was just thinking it would be great to be able to visualize all of the pages, and adding the STP category would be a good way to do that :) > It seems using "subfolders" like STP/BPMN actually generates the STP/BPMN page. > > Would it be possible to move the component home pages to that address ? It > would certainly help people to find their way around. That's right, and I do use this mechanism. You will see that the home page for the BPMN component is STP/BPMN_Component when you move links to your page, you should also do a 'wiki' move, changing their name to STP/BPMN_Component/<PageName> then when you navigate to <PageName> there will be a little breadcrumb trail up at the top left of the page which helps people know where they can go 'back up'.
ok, so all pages must relate to the SOA category, and we should use: STP/BPMN_Component/<PageName> I had started working with STP/BPMN/<PageName>. I'll get around this quickly. Thanks!
I found out that referencing the SOA category on your category page would mark it as a subcategory. I think we can keep with tagging our component pages with our subcategory tag, as long as it is related to SOA as a subcategory. Allright ?
(In reply to comment #7) > I found out that referencing the SOA category on your category page would mark > it as a subcategory. That's strange - I don't think that was what was meant to happen. For example, the Modeling category on the end of the page doesn't mean that BPMN has become a subcategory of Modeling (I checked it). May a SOA/BPMN category has been introduced somewhere by accident? > I think we can keep with tagging our component pages with our subcategory tag, > as long as it is related to SOA as a subcategory. > > Allright ? It's ok not to have SOA as a category on your page, but I would like it if you had STP as a category so that I can then see all of the STP-related pages just by looking at the category index. Does that make sense?
(In reply to comment #8) > (In reply to comment #7) > > I found out that referencing the SOA category on your category page would mark > > it as a subcategory. > > That's strange - I don't think that was what was meant to happen. For example, > the Modeling category on the end of the page doesn't mean that BPMN has > become a subcategory of Modeling (I checked it). No, it doesn't work like that. The category page is: http://wiki.eclipse.org/Category:BPMN If you go there, you will see that I added [[Category:SOA]] on it. The SOA category (http://wiki.eclipse.org/Category:SOA) will reference it then. > > May a SOA/BPMN category has been introduced somewhere by accident? > > > I think we can keep with tagging our component pages with our subcategory tag, > > as long as it is related to SOA as a subcategory. > > > > Allright ? > > It's ok not to have SOA as a category on your page, but I would like it if you > had > STP as a category so that I can then see all of the STP-related pages just by > looking > at the category index. > > Does that make sense? > Yes, it'd be pretty. Ok, so I need to make BPMN a subcategory of STP, and have all the wiki pages categorized as STP. :P
(In reply to comment #9) > No, it doesn't work like that. The category page is: > > http://wiki.eclipse.org/Category:BPMN > > If you go there, you will see that I added [[Category:SOA]] on it. > > The SOA category (http://wiki.eclipse.org/Category:SOA) will reference it then. Ding! The penny drops. So I see you are constructing a hierarchy of Categories which mirrors the hierarchy of pages, at least for a few nodes of depth. These seems like a good plan. > > It's ok not to have SOA as a category on your page, but I would like it if you > > had > > STP as a category so that I can then see all of the STP-related pages just by > > looking > > at the category index. > > > > Does that make sense? > > > Yes, it'd be pretty. Ok, so I need to make BPMN a subcategory of STP, and have > all the wiki pages categorized as STP. :P Not just pretty, useful too! My brain doesn't work like a wiki you see, and if I can do an HTTP GET to get a list of all the pages that relate to STP then I can hack up a client which will draw it all out as a more understandable (to me) tree :)
ok, all done. Can you have a look at this page ? http://wiki.eclipse.org/index.php?title=Category:STP&action=edit and write something pretty there. Thanks!
(In reply to comment #11) > ok, all done. > > Can you have a look at this page ? > http://wiki.eclipse.org/index.php?title=Category:STP&action=edit > > and write something pretty there. Done!
The Infobox template could be useful as well: http://wiki.eclipse.org/Template:Infobox I added it to the BPMN component page.
Moved to P1 for Ganymede.
*** Bug 265829 has been marked as a duplicate of this bug. ***
Deadlinks on http://wiki.eclipse.org/Installing_Headless_Buckminster 404 when trying to download director app, also the text on the page makes it unclear whether this is a updatesite-url or this is a real 404. This is not the only deadlink it seems the eclipse wiki and the eclipse.org is full of this links
