-
1. Re: Confused about infrastructure (SVN, Mailinglist, ...)
camunda Jul 2, 2008 3:42 AM (in response to camunda)One more: Why there is a second wiki on jbpm.dyndns.org? So which one should be used? The JBoss-Wiki? Or this special wiki?
-
2. Re: Confused about infrastructure (SVN, Mailinglist, ...)
camunda Jul 2, 2008 3:44 AM (in response to camunda)Okay, found something in that second wiki:
http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3BuildingFromSource
Seems this ( svn co https://svn.jboss.org/repos/jbpm/jbpm3/trunk) is the correct SVN for all future commits in 3.x then? -
3. Re: Confused about infrastructure (SVN, Mailinglist, ...)
heiko.braun Jul 2, 2008 8:13 AM (in response to camunda)Right, part of the infrastructure consolidation was the move to subversion. The repo you pointed to, is the current one.
-
4. Re: Confused about infrastructure (SVN, Mailinglist, ...)
heiko.braun Jul 2, 2008 8:14 AM (in response to camunda)
One more: Why there is a second wiki on jbpm.dyndns.org? So which one should be used? The JBoss-Wiki? Or this special wiki?
The new one. We are going to migrate contents to that instance soon.
However if you need to update or create new content, please do it in the new WIKI right away. -
5. Re: Confused about infrastructure (SVN, Mailinglist, ...)
kukeltje Jul 2, 2008 9:44 AM (in response to camunda)it's not so much the changing but the inconsistency, uncertainty etc that arises when things are announced and announced and...
e.g. the full jBPM site (jbpm,jpdl,bpel,gpd) point to the cvs, 'old' wiki etc...
On the one hand we (jBPM community within jBoss) try to achieve consistency (e.g. moving to cvs) but go to a separate new wiki, (not top mention the seam guys with a full separate (but in some ways more usable) site... Why is this INconsistency arising?
I've heard some rumours about a realy new wiki.... (and why not new forums? the've been announced way back, with good search functionality, not the sh*t that spits out results now)
That is where consistency should be... not the one thing about cvs/svn or the (and I agree with Bernd here) unnecessary introduction of the dev mailing list (just because other projects use it as well....
Just my €0.01 -
6. Re: Confused about infrastructure (SVN, Mailinglist, ...)
heiko.braun Jul 2, 2008 10:14 AM (in response to camunda)
the inconsistency...
is just a temporal thing. It needs to start somwhere and incrementally move to the right direction. The WIKI will be tackled next. -
7. Re: Confused about infrastructure (SVN, Mailinglist, ...)
heiko.braun Jul 2, 2008 10:21 AM (in response to camunda)
some rumours about a really new wiki.
yep, that's supposed to be on the way. However will it really fit our needs? Who knows. Currently we take was has been proven successful for other projects. The foremost reason for the custom mediawiki is that we want to get rid of docbook references at all. It will all be compiled from the wiki, regardless if it's user or developer contribution to the docs.
This leaves us with one source for documentation and eliminates the redundancy between docbook and wiki docs.
And you know: The people only write documentation if it's easy todo so.
That includes maintenance as well. -
8. Re: Confused about infrastructure (SVN, Mailinglist, ...)
koen.aers Jul 2, 2008 12:30 PM (in response to camunda)I'll take care of the website.
Regards,
Koen -
9. Re: Confused about infrastructure (SVN, Mailinglist, ...)
tom.baeyens Jul 5, 2008 2:48 PM (in response to camunda)"kukeltje" wrote:
it's not so much the changing but the inconsistency, uncertainty etc that arises when things are announced and announced and...
point taken.
we should discuss changes better with the community and see how the proposed change is an improvement in the context of what is available. -
10. Re: Confused about infrastructure (SVN, Mailinglist, ...)
kukeltje Jul 6, 2008 3:48 PM (in response to camunda)it's not even that... at least not to a big extend. Moving to SVN is fairly obvious... better release cycles also.. it's the thing that it should have been in an overview document, posted on a very visible part in the site, wiki, forum, so everybody (not only the core people) can see what is going on in times of change
-
11. Re: Confused about infrastructure (SVN, Mailinglist, ...)
thomas.diesler Jul 7, 2008 3:07 AM (in response to camunda)Hi Ronald,
we are in the process of major clean up and restructuring. Areas that are effected are:
* usage of mailing lists
* wiki documentation
* source repository
* build process
* automated test coverage
* release procedure
* API design
If you look at these areas on-by-one, you sure realize that there is much needed work to be done. Due to the open nature of our development process it unavoidable (and even desired) that the community sees snapshots of the work in progress.
We have by no means completed that restructuring yet - please stay with us through this part of a bumpy road - you can take my word that by the end of this year, you will find an infrastructure that is far superior to what was there up until jbpm-3.2.3 and much more enjoyable to work with for everybody.
cheers -
12. Re: Confused about infrastructure (SVN, Mailinglist, ...)
kukeltje Jul 7, 2008 5:04 AM (in response to camunda)Thomas,
Thanks for the summary... It's kind of what I grasped from all separate things going on. Others not so close to the project might get a wrong idea... dead links, out of date docs etc...
Maybe this summary should be a sticky post in both forums with links to (wiki) pages where more info can be found. It'll cost me less time to keep 'the community' lined up....
Besides this, I agree that the new infrastructure is superiour and is a good move... (new forums also? pleeeeaaassseeee ;-) ) -
13. Re: Confused about infrastructure (SVN, Mailinglist, ...)
thomas.diesler Jul 7, 2008 5:06 AM (in response to camunda)yes, we are probably moving to clearspace for all jboss.org forums.
-
14. Re: Confused about infrastructure (SVN, Mailinglist, ...)
koen.aers Jul 7, 2008 5:23 AM (in response to camunda)On our website there is a 'tbd' page for the community. Maybe I should summarize the planned and executed changes there? Or should I just refer to a wiki page?
What do you guys think?
Regards,
Koen