[Geany] Moving contents from newsletter.geany.org into the wiki?

[Russell Dickenson]

On 6 June 2011 10:50, Matthew Brush <mbrush at codebrainz.ca> wrote:
> On 06/04/11 17:32, Matthew Brush wrote:
>>
>> On 06/03/11 07:44, Enrico Tröger wrote:
>>>
>>> Hi,
>>>
>>> what do you wiki and newsletter guys think of the following idea:
>>>
>>> we move most of the current content of http://newsletter.geany.org/
>>> into the wiki, for testing purpose, I already did it (please note this
>>> is just for testing and to get your feedback).
>>>
>>> In the wiki the latest volumes are linked, the newsletter files
>>> themselves remain on newsletter.g.o.
>>>
>>> On newsletter.geany.org we would simply show the latest volume's HTML
>>> page directly and maybe a link on the bottom to the wiki page.
>>>
>>> What do you think?
>>>
>>
>> On a related topic, what if any useful HowTo, explanation, or plugin
>> review that is destined for the newsletter *must* (should) be added to
>> the wiki first. Then the new content from the wiki can be formatted into
>> the newsletter proper (using proper markup, etc), probably having a
>> link/ref back from the newsletter to the wiki. This way, the wiki is
>> always benefiting from the relevant parts of the newsletter and even if
>> reading an old newsletter issue, the current parts can be found on the
>> wiki though links/refs embedded in the newsletter. Another benefit of
>> this is that anyone can potentially contribute stuff to the newsletter
>> without worrying about the markup/presentation of the newsletter. This
>> is best left to specialists, IMO.
>>
>> Just an idea.
>>
>
> Hi,
>
> To clear up what I meant here.  I was proposing certain little bits of the
> newsletters, such as a HowTo or other instructions (stuff that belongs in a
> wiki also), be added to the Wiki.  Somewhere in say a references section in
> the newsletter there could be a link back to the wiki like "see Some
> Tutorial on the wiki for the latest information".
>
> The point being to share the effort between the wiki and newsletters for the
> small area where they overlap.  I see no point in having an immutable page
> of the original content from the newsletter or any of that jazz.
>
> Here's an example:
> We decide to add an overview on using GeanyFooPlugin to the newsletter and I
> should be the one to write it.  Since it's a tutorial and fits well in the
> Wiki, I would go to the wiki and make a new page under Howtos called "Using
> GeanyFooPlugin".  I and others would hack on that until the newsletter is
> due to be published.  At that point, one of the newsletter publishers/markup
> ninjas (Frank, for ex) would take the content form the "Using
> GeanyFooPlugin" wiki page and properly format it into the newsletter issue
> (possibly editing/shortening it, etc). Obviously the Wiki page is going to
> continue to be edited and the newsletter won't be, which is fine, but at
> least both of the two benefited from the same effort, and I never had to
> learn a new markup language :)
>
> Cheers,
> Matthew Brush

That's how I understood your proposal, Matthew, and I think it's a
good idea. The newsletter should be published in its original format
for future reference. However the content which has a useful life past
the publication date of the newsletter certainly could and I think
*should* be in the wiki.

The benefit of this approach is:

* HowTo information is highlighted in the newsletter and is easily
read and understood;
* Anyone who can edit the wiki is able to contribute to the newsletter;
* Useful reference information remains in the wiki, to be added to and
enhanced over time.

I currently write the newsletter of Frugalware Linux. Over the few
years I've been writing, I have written some things which are still
useful reference information. However they're contained in the
newsletter, not the wiki and so not easily found, nor edited. Putting
this information first into the wiki would have avoided this problem.


-- 
Russell Dickenson