From: Dill <sarpulhu@gmail.com>
To: git@vger.kernel.org
Subject: Re: Git Wiki improvements
Date: Sun, 13 Apr 2008 19:25:41 -0700 (PDT) [thread overview]
Message-ID: <8c25cb7a-a544-4464-b0ac-c95f99b349a0@2g2000hsn.googlegroups.com> (raw)
In-Reply-To: <200804140303.22624.jnareb@gmail.com>
The more I think of it... maybe it's best to leave the wiki alone.
It's not broken...it's just not great. Maybe we should just leaves
things as they are? I'm sure we can work around the problems the
software sometimes gives us. But on the other hand a move to
git.kernel.org would be easier to use it's just a lot of work to move
it over there. Anyone else have complaints about the wiki? Or maybe
I'm the only one. ;)
On Apr 13, 7:03 pm, Jakub Narebski <jna...@gmail.com> wrote:
> [Cc: g...@vger.kernel.org, Petr Baudis <pa...@suse.cz>]
>
>
>
>
>
> Pack, Dylan wrote:
> > Jakub Narebski wrote
> >> On Mon, 14 April 2008, Pack, Dylan wrote:
>
> >>> I've noticed to that the wiki gets mixed up if I use the GUI editor.
> >>> Looks like I'm going to have the syntax after all of well.
>
> >> Unfortunately Git Wiki administrator (Petr Baudis, who also maintains
> >> git homepage), doesn't have much time to spend on configuring wiki,
> >> and doesn't know well MoinMoin. The problem seems to lie in the fact
> >> that Wikipedia-like (or rather MediaWiki-like) syntax provided by
> >> (I guess) media4moin plugin doesn't modify GUI editing. This affect
> >> mosts macros, which in default MoinMoin syntax are written as
> >> e.g. [[BR]], while Wikipedia-like syntax uses e.g. {{BR}}.
>
> > Perhaps a move to wikidot.com would work? They have an awesome set up
> > for wikis. I've tried them out and they are fast and always improving
> > the wiki. We could even add google adsense on the wikidot site for
> > money to be put into various git projects decided on by the
> > developers. Not sure how much money though a git wiki site would make.
>
> I'm not sure if it is a good idea. We would loose a bit control, and
> would have git homepage and git wiki in separate domains. On the other
> hand some of admin stuff would be passed to wiki hosting site.
> Bazaar-NG, Mercurial and Monotone (and also Emacs) have their own self
> hosted wikis.
>
> Git homepage at git.or.cz (or git-scm.org), Git Wiki at
> git.or.cz/gitwiki and free git hosting at repo.or.cz are all provided
> by Petr 'Pasky' Baudis (thanks a lot, again!).
>
> By the way, Git Wiki initially began as a "staging ground" for contents
> which would get incorporated into Git Homepage...
>
> --
> Jakub Narebski
> Poland
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html- Hide quoted text -
>
> - Show quoted text -
next prev parent reply other threads:[~2008-04-14 2:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <60CC37BF5A3B73428D0BB9B6A26B9669019D95DA@yvrmail1.corp.navcan.ca>
2008-04-14 1:03 ` Git Wiki improvements Jakub Narebski
2008-04-14 1:11 ` Dill
2008-04-14 1:20 ` Dill
2008-04-14 1:40 ` J.H.
2008-04-14 1:47 ` Dill
2008-04-14 2:25 ` Dill [this message]
2008-04-14 8:06 ` Santi Béjar
2008-04-14 14:58 ` Johannes Schindelin
2008-04-14 15:48 ` Sean Estabrooks
2008-04-14 16:03 ` Johannes Schindelin
2008-04-14 16:18 ` Jeremy Maitin-Shepard
2008-04-14 16:53 ` Sean Estabrooks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8c25cb7a-a544-4464-b0ac-c95f99b349a0@2g2000hsn.googlegroups.com \
--to=sarpulhu@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).