Ok. I cannot find any way to create a personal space on the Apache wiki (so I can test the interface) without contacting the ASF infrastructure team. So, I guess we would have to create a Confluence wiki, if we want to try it out.
If so, this is what we need to tell them: wiki name -- TavernaDev (?) - this would distinguish it from the other "official/public" wikis that all start with Apache ... destination for commit mails -- (not 100% sure what this is referring to) confluence usernames of two+ community members - volunteer space admins -- I am willing to be one (gnaylor) What do you think? Gale On Tue, Feb 16, 2016 at 12:02 PM Gale Naylor <[email protected]> wrote: > I agree that a wiki-type approach (for internal/ in-progress work) where > everyone can edit directly would be best (and most efficient). > > The Confluence wiki seems to be designed for what we want to do, although > I wish you could use Markdown. (I was hoping to create a personal space on > the wiki to see how difficult it would be to transfer the output to > Markdown, but I have yet to be able to create a space.) Even though this is > a WYSIWYG editor, couldn't we write it in Markdown anyway, making it a > little more difficult to read but easier to transfer? > > Since using Markdown pages in the incubator-taverna-site has the same SVN > issues as raised in https://issues.apache.org/jira/browse/TAVERNA-870, > would that create a lot more work merging the pull requests? > > What would be easiest/quickest right now? The Confluence wiki? Maybe we > could live with whichever option for working on the release notes, and I > will try to look at Jekyll and Maven Site to see if I have any thoughts on > which one might be a good path for the future? > > Gale > > On Tue, Feb 16, 2016 at 9:15 AM Stian Soiland-Reyes <[email protected]> > wrote: > >> Hi, >> >> Gale has drafted release notes on >> >> https://galenaylor.wordpress.com/2016/02/01/draft-taverna-language-release-notes-2/ >> >> however I feel I want to 'edit' them rather than respond by email.. >> >> would it be more natural to edit this in a developer wiki? >> >> >> We can ask to get a TAVERNADEV space at https://cwiki.apache.org/ ? >> >> >> Alternatively we can do it as markdown pages in a folder under >> https://github.com/apache/incubator-taverna-site/ (say a folder 'wiki' >> or 'dev') - but sadly that's (currently) edited by SVN rather than git >> - see also https://issues.apache.org/jira/browse/TAVERNA-870 -- also >> then non-committers can't contribute except by pull request. >> >> >> One advantage of Markdown-in-folder the markdown files could be >> directly transferable to the normal Taverna web-space, while the >> Confluence wiki uses an internal WYSIWYG format which is harder to >> move. >> >> >> Note that I mean just for internal in-progress stuff, not >> documentation for external users - although >> that's a separate issue to try to transfer the documentation wiki from >> http://dev.mygrid.org.uk/wiki/display/tav250 to Apache's confluence. >> (This is a bit more work because of version mismatch) >> >> >> (Ideally I would have preferred a GitHub wiki, but that would have >> been hosted outside Apache's infrastructure) >> >> >> -- >> Stian Soiland-Reyes >> Apache Taverna (incubating), Apache Commons RDF (incubating) >> http://orcid.org/0000-0001-9842-9718 >> >
