+1 docs in git with Markdown
-
PATATE12
jesus2099
GOLD MASTER KING
FAKE E-MAIL ADDRESS
--
View this message in context:
http://musicbrainz.1054305.n4.nabble.com/Changes-to-our-style-process-Important-tp4668864p4669298.html
Sent from the MusicBrainz - Style mailing list archive at
Using git as a wiki replacement can be a good idea and can be easy to do if
you know how.
Github encourages you to use a text document using markdown.
Markdown is a wiki like language and can be easily converted into html.
Editing a markdown in github is just as easy as editing a wiki page.
First
On 10/30/2014 05:58 PM, Ben Ockmore wrote:
I do still think that putting it all on Git is a good idea though
(especially given the online editing capabilities of GH and BB). Just
not TT templates, and separate from the server code.
For anybody interested, keep an eye on
On 29/10/2014 23:24, Ian McEwen wrote:
On Wed, Oct 29, 2014 at 10:55:53PM +, Tom Crocker wrote:
Out of interest, does this mean we're getting rid of the distinction
between official style guidelines and docs? Or are docs still open to
community editing?
Any moving things into the codebase
On 30/10/2014 13:54, Nicolás Tamargo de Eguren wrote:
On Thu, Oct 30, 2014 at 3:11 PM, Paul Taylor ij...@fastmail.fm
mailto:ij...@fastmail.fm wrote:
I disagree, although one person is currently has now been put in
charge
of the style process this is a new change that may need
Yeah, I have to agree with Paul, making documentation editors edit HTML
templates is an unnecessary complication, when there are plenty of existing
plain text to HTML conversion systems which would work just as well.
AFAIK our current system doesn't require any data from the rest of the
server,
On Sun, 2014-10-26 at 23:00 +0100, Robert Bihlmeyer wrote:
Am 2014-10-23 22:27, schrieb Frederic Da Vitoria:
2014-10-23 22:08 GMT+02:00 Robert Bihlmeyer ro...@orcus.priv.at:
Can we get versioned (or time stamped) style documents?
Am I missing something or wouldn't the wiki history
I very much agree with this. While having only one person editing docs may
be a good idea for ensuring consistency and quality, it also rules out the
main advantage of storing docs in a wiki.
It'd probably simplify things if all the docs were written in Markdown or
RST, then displayed as static
On Wed, Oct 29, 2014 at 12:14:39PM -0400, Calvin Walton wrote:
On Sun, 2014-10-26 at 23:00 +0100, Robert Bihlmeyer wrote:
Am 2014-10-23 22:27, schrieb Frederic Da Vitoria:
2014-10-23 22:08 GMT+02:00 Robert Bihlmeyer ro...@orcus.priv.at:
Can we get versioned (or time stamped) style
Out of interest, does this mean we're getting rid of the distinction
between official style guidelines and docs? Or are docs still open to
community editing?
___
MusicBrainz-style mailing list
MusicBrainz-style@lists.musicbrainz.org
On Wed, Oct 29, 2014 at 10:55:53PM +, Tom Crocker wrote:
Out of interest, does this mean we're getting rid of the distinction
between official style guidelines and docs? Or are docs still open to
community editing?
Any moving things into the codebase doesn't change the 'community
editing'
Am 2014-10-23 22:27, schrieb Frederic Da Vitoria:
2014-10-23 22:08 GMT+02:00 Robert Bihlmeyer ro...@orcus.priv.at:
Can we get versioned (or time stamped) style documents?
Am I missing something or wouldn't the wiki history answer this need?
Style is currently split into more than 30 wiki
Nicolás Tamargo de Eguren wrote
On Thu, Oct 23, 2014 at 1:25 AM, David Gasaway lt;
dave@
gt; wrote:
On Sun, Oct 19, 2014 at 10:42 AM, Nicolás Tamargo de Eguren
lt;
reosarevok@
gt; wrote:
tl;dr: Style system has changed, new info at
http://musicbrainz.org/doc/Proposals
Hi. How
On 2014-10-23 16:34 lixobix wrote:
Is there a way to get email updates when the blog is updated?
I don't think so. But http://blog.musicbrainz.org/feed/ is an RSS feed,
that most popular mail user agents know how to handle. There are also
phone apps for twitchers.
See
On 2014-10-23 00:30, Nicolás Tamargo de Eguren wrote:
For checking what changes have happened, we'll be posting on the blog
(category Style) a list of implemented changes every two weeks (more or
less).
Can we get versioned (or time stamped) style documents?
That would make it possible to look
On Oct 23, 2014, at 3:08 PM, Robert Bihlmeyer ro...@orcus.priv.at wrote:
On 2014-10-23 00:30, Nicolás Tamargo de Eguren wrote:
For checking what changes have happened, we'll be posting on the blog
(category Style) a list of implemented changes every two weeks (more or
less).
Can we get
2014-10-23 22:08 GMT+02:00 Robert Bihlmeyer ro...@orcus.priv.at:
On 2014-10-23 00:30, Nicolás Tamargo de Eguren wrote:
For checking what changes have happened, we'll be posting on the blog
(category Style) a list of implemented changes every two weeks (more or
less).
Can we get versioned
On Sun, Oct 19, 2014 at 10:42 AM, Nicolás Tamargo de Eguren
reosare...@gmail.com wrote:
tl;dr: Style system has changed, new info at
http://musicbrainz.org/doc/Proposals
Hi. How should an editor keep abreast of style changes under the new system?
--
-:-:- David K. Gasaway
-:-:- Email:
On Thu, Oct 23, 2014 at 1:25 AM, David Gasaway d...@gasaway.org wrote:
On Sun, Oct 19, 2014 at 10:42 AM, Nicolás Tamargo de Eguren
reosare...@gmail.com wrote:
tl;dr: Style system has changed, new info at
http://musicbrainz.org/doc/Proposals
Hi. How should an editor keep abreast of style
Nicolás Tamargo de Eguren wrote
Hi! So, this has already been posted to the blog, but for those here who
don't read the blog, I'll repost:
At the MusicBrainz Summit last month in Copenhagen, one of the topics to
be discussed was the state of the style guidelines and style process.
One thing
Hi! So, this has already been posted to the blog, but for those here who
don't read the blog, I'll repost:
At the MusicBrainz Summit last month in Copenhagen, one of the topics to
be discussed was the state of the style guidelines and style process.
One thing those present agreed on was that the
21 matches
Mail list logo
