new SF features

Related to comments to Christian earlier today …

All,

I just accidentally stumbled on the fact that SF has added a bunch of
majorly kick-ass new features. Here’s just a small list of the
options, in this case the ones I enabled.

git
trac
laconica (like twitter, but better and free)
wiki
wordpress

So, as time permits, I’m going to look into reworking the site to take
advantage of this. This gives an opportunity to really rethink the
infrastructure of the site.

Any particular thoughts on any of this?

THe one obvious issue that has relevance to the code is version
control. I’m a fan of distributed SCMs like git and darcs. Is there
any reason we shouldn’t move over the following to git?

csl schema
citeproc implementations (js, python, ruby)

I also need to figure out whether I can get Trac to support git,
though. With the enhancements to the default SF tracker, this may not
be needed in any case.

Finally, I need to figure out if I can get SG to map the current
project URLs to the wordpress install, which is currently at:

https://apps.sourceforge.net/wordpress/xbiblio/

Laconica is, of oourse, at:

https://apps.sourceforge.net/lcaonica/xbiblio/

Finally, any suggestions on a Wordpress theme?

Bruce

Related to comments to Christian earlier today …

All,

I just accidentally stumbled on the fact that SF has added a bunch of
majorly kick-ass new features. Here’s just a small list of the
options, in this case the ones I enabled.

git
trac
laconica (like twitter, but better and free)
wiki
wordpress

So, as time permits, I’m going to look into reworking the site to take
advantage of this. This gives an opportunity to really rethink the
infrastructure of the site.

Any particular thoughts on any of this?

THe one obvious issue that has relevance to the code is version
control. I’m a fan of distributed SCMs like git and darcs. Is there
any reason we shouldn’t move over the following to git?

csl schema
citeproc implementations (js, python, ruby)

I’m easy, whatever you decide. I’ve never used git before, but on a
quick look it seems easy to adapt to coming from subversion.

Frank

I think, for now, I’m going to stick with SVN, but leave the git support on.

But I’d like to use this opportunity to think: what do we need to do
to realize CSLs’ potential?

Clearly in general we need to:

  1. finish the schema and declare it 1.0.

  2. create real documentation for style authors, implementors, and
    publishers/journals

  3. create a test suite, so that we have some metric to …

  4. … say we’ve got fully-working implementations in javascript,
    haskell, p;ython and ruby

  5. promote CSL, particularly to publishers/journals

The question is how we to this, and whether the new SF stuff can help us.

Bruce

Now that CSL is rapidly gaining new features, I guess some up-to-date
documentation on the schema for style authors wouldn’t hurt. Do you think it
is a good idea to just copy the stuff from the Zotero wiki (
http://www.zotero.org/support/dev/creating_citation_styles and
http://www.zotero.org/support/dev/csl_syntax_summary) to the wiki provided
by Sourceforge, and to add all the new stuff (while indicating that those
new features are not yet available in CSL 0.8)?

Rintze

That might make sense.

But then we have a followup question: which wiki?

Right now, we have the one I turned on (forget the name), the one
built into Trac, and we can also use MediaWiki. Which is best for
these purposes?

Bruce2009/3/23 Rintze Zelle <@Rintze_Zelle>:

Are all those three options hosted by Sourceforge? I’m happy as long as the
documentation is close to the schema (so it no longer depends on external
sources like the Zotero wiki) and if the wiki supports XML syntax
highlighting. Using the Trac wiki only seems logical if Trac will also be
used to keep track of the CSL tickets.

Rintze

How about this one?

http://en.blog.wordpress.com/2008/09/12/depo-masthead-theme-launch/

I need to be semi-committed to whatever choice, as I need to put in a
request with the SF team to add it.

Still haven’t decided if we really need this, but if we use it, it’d
be for updates on CSL and efforts around it. I am not sure, but I
think that any project member would be able to post.

Bruce