[GMG-Devel] wiki: the very beginning
jwcampbell at gmail.com
Thu Jul 14 13:14:21 EDT 2011
I'm a bit new here, but have done work on GNOME and Ubuntu docs, as well as
some documentation for a couple of small Xfce programs.
On Thu, Jul 14, 2011 at 9:14 AM, will kahn-greene <willg at bluesock.org>wrote:
> I set up a wiki at:
> It's working, but it's bereft of any content so far.
Thanks for getting that set up!
> Yesterday, Elrond and I were talking about the wiki and that conversation
> brought up a few things, so I figured I'd run it by people on this list to
> see if what I've got set up is ok for now or not.
> 1. Elrond mentioned openid support. redmine has openid support, so if the
> wiki did, too, then theoretically someone could use their openid thingy and
> sign into both places.
> Does that help anyone on this list? If not, I'm not going to spend the
> time to get it working right now.
I appreciate when sites have OpenID logins available, but it isn't a
deal-breaker for me.
> 2. The instance is set up such that:
> * you need an email-verified account to edit
> * you need to be in the uploadaccess group to upload files
> I think I want to add a captcha for when someone tries to save a page with
> links to external sites, but I may wait on that until we need it.
> Now we get to the part I have fewer opinions on. With the addition of the
> wiki, we now have three places for documentationy things:
> * the mediagoblin.org web-site
> * the wiki
> * the docs/
> I was thinking that since docs/ is versioned alongside the software with
> the actual release that it should be a self-contained manual for the
> software with links back to the wiki and the web-site for things that don't
> really change much between versions (details about our IRC channel and
> mailing list, our general vision, ...).
Right now the docs have separate sections for users, administrators, and
people who want to contribute to the project. I can put together a quick
content inventory of what is documented now so that it will be easier to
decide what should go where.
I agree that it isn't what should go where, but also who is likely to
maintain the information, and how can we make it easiest for them to
contribute now and in the future.
> The wiki is the easiest place for people to change content, so recipes for
> setting up MediaGoblin on different Linux distributions and other operating
> systems should definitely go there.
> The web-site is our outward facing site that is more marketing/pr oriented
> than the other two locations. So blog entries, press releases, and things
> like that should go on the web-site.
> I'm pretty sure it's the case that we will have some content duplicated
> between the three places. I'm ok with that, though the less the better
> since it requires more work to keep updated.
> How does that sound? Do you have other ways to figure out which content
> should go where?
This sounds good. As for duplicate documentation - I think it's ok if the
information isn't likely to change (about mediagoblin, getting in touch,
I'll put a content inventory with some suggestions together and make it
available by by tomorrow.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the devel