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?
Regards, Enrico
Am 03.06.2011 16:44, schrieb Enrico Tröger:
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?
I don't care much about. I would be fine with every decision.
Cheers, Frank
Am Freitag, den 03.06.2011, 16:44 +0200 schrieb Enrico Tröger:
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.
I definitely see the advantage for having such informations also in the wiki, but I don't see why we should remove informations from newsletter.geany.org.
From perspective of a user who is searching for old volumes of the Newsletter, I'd go to newsletter.geany.org and be frustrated if I was not able to find them there. I'd never come to the thought to search in the wiki for that.
From my technical and rational point of view: The listing with the newsletter volumes is generated automatically. The list in the wiki has to be maintained manually. Well...see my point? ;)
Regards, Dominic
On Sat, 04 Jun 2011 09:35:52 +0200, Dominic wrote:
Am Freitag, den 03.06.2011, 16:44 +0200 schrieb Enrico Tröger:
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.
I definitely see the advantage for having such informations also in the wiki, but I don't see why we should remove informations from newsletter.geany.org.
By cleaning up newsletter.geany.org we could use the current newsletter issue as index page for the site which I think would be cool. If you really want, we could add some kind of footer (or a small header) to link to the Wiki as well as the autogenerated index page. So, users can just point their browser to newsletter.geany.org and always get the latest newsletter issue presented without any further clicks.
From perspective of a user who is searching for old volumes of the Newsletter, I'd go to newsletter.geany.org and be frustrated if I was not able to find them there. I'd never come to the thought to search in the wiki for that.
Maybe. This could be solved by a header or footer, see above.
From my technical and rational point of view: The listing with the newsletter volumes is generated automatically. The list in the wiki has to be maintained manually. Well...see my point? ;)
Not at all. Making a new newsletter issue is always manual work, this is not an automated process and so I think adding a line which is mostly copy&paste in the wiki, isn't the worst thing ever. Whatever, I'd happy to do this if it seems like a hard task.
Regards, Enrico
On Sat, 4 Jun 2011 11:05:29 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
On Sat, 04 Jun 2011 09:35:52 +0200, Dominic wrote:
From my technical and rational point of view: The listing with the newsletter volumes is generated automatically. The list in the wiki has to be maintained manually. Well...see my point? ;)
Not at all. Making a new newsletter issue is always manual work, this is not an automated process and so I think adding a line which is mostly copy&paste in the wiki, isn't the worst thing ever. Whatever, I'd happy to do this if it seems like a hard task.
Well, at least here I need support Dominic. Its just another small piece of work which might is not needed.
Cheers, Frank
Am Samstag, den 04.06.2011, 11:11 +0200 schrieb Frank Lanitz:
On Sat, 4 Jun 2011 11:05:29 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
On Sat, 04 Jun 2011 09:35:52 +0200, Dominic wrote:
From my technical and rational point of view: The listing with the newsletter volumes is generated automatically. The list in the wiki has to be maintained manually. Well...see my point? ;)
Not at all. Making a new newsletter issue is always manual work, this is not an automated process and so I think adding a line which is mostly copy&paste in the wiki, isn't the worst thing ever. Whatever, I'd happy to do this if it seems like a hard task.
My suggestion to handle this:
* have a symlink named index.html pointing to the actual newsletter * have a page (e.g. newsletters.php) where all newsletters are listed anyway * link from the newsletter to the newsletters.php
First two points are already done, so if you visit newsletters.geany.org now, the newsletter vol 2 is the landing page. The third point still has to be done, though.
I think the symlink is a quite nice idea here.
Regards, Dominic
First two points are already done, so if you visit newsletters.geany.org now, the newsletter vol 2 is the landing page. The third point still has to be done, though.
Hi Dominic,
So I am a new visitor and I go from the Geany website to newsletter 2 or what ever is the current one, then how do I get any of the others?
Cheers Lex
Am Montag, den 06.06.2011, 09:45 +1000 schrieb Lex Trotman:
First two points are already done, so if you visit newsletters.geany.org now, the newsletter vol 2 is the landing page. The third point still has to be done, though.
Hi Dominic,
So I am a new visitor and I go from the Geany website to newsletter 2 or what ever is the current one, then how do I get any of the others?
As I said, those links have still to be implemented, most likely into the newsletters itself, including the current vol 2. Or did I misunderstood the previous suggestions from Enrico and so on?
Regards, Dominic
On Wed, 08 Jun 2011 23:53:49 +0200, Dominic wrote:
Am Montag, den 06.06.2011, 09:45 +1000 schrieb Lex Trotman:
First two points are already done, so if you visit newsletters.geany.org now, the newsletter vol 2 is the landing page. The third point still has to be done, though.
Hi Dominic,
So I am a new visitor and I go from the Geany website to newsletter 2 or what ever is the current one, then how do I get any of the others?
Is this necessary? The page from which the user initially came, could have links to the older issues or to an autogenerated index. Or, I think I said this earlier somewhere already, add a short link to the HTML newsletter (on newsletter.g.o) to refer to the wiki or so.
However, I don't have a strong opinion on this. And is this still relevant at all regarding to the other part of this thread?
As I said, those links have still to be implemented, most likely into the newsletters itself, including the current vol 2. Or did I misunderstood the previous suggestions from Enrico and so on?
I have no good idea how to handle it, so I leave this up too you.
Regards, Enrico
Or, I think I said this earlier somewhere already, add a short link to the HTML newsletter (on newsletter.g.o) to refer to the wiki or so.
Yes, just have the geany website have two links, one to the current newsletter, one to the wiki page with all the newsletters, that would work fine.
Cheers Lex
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.
Cheers, Matthew Brush
On Sat, 04 Jun 2011 17:32:21 -0700 Matthew Brush mbrush@codebrainz.ca 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.
Do I understand you correct, that newsletter should work more as some kind of teaser for HowTo articles? Somehow I like that idea.
Cheers, Frank
On Sunday 05 June 2011 04:20:25 am Frank Lanitz wrote:
On Sat, 04 Jun 2011 17:32:21 -0700 Matthew Brush mbrush@codebrainz.ca wrote:
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.
Do I understand you correct, that newsletter should work more as some kind of teaser for HowTo articles? Somehow I like that idea.
I like Matthew's idea a lot, but I don't think what he described is quite like a teaser. It is more like the wiki becomes the canonical location for the information disclosed in the newsletter.
When I say it that way, it is more like the newsletter is the teaser for the wiki, but I wouldn't suggest that either.
IMO, the newsletter should contain good, complete (i.e., self-contained) articles on some subject. The article should contain a link to a wiki page that is, at least at one point in time, the text of the article.
Potential newsletter articles might (well, I'd like to say should--there may be exceptions, perhaps due to deadline pressure) be posted on the wiki. Others can review those potential articles and make or suggest improvements in the wiki way.
(There might be a notice on the page saying either that the wiki page is proposed as a newsletter article (by the writer or someone else), or is anticipated to be (i.e., tentatively, at least, accepted as a newsletter article.)
When the article is published in the newsletter, there is a link to the wiki page.
After the newsletter article is posted, the page remains on the wiki and (in the wiki way) is corrected and updated as time goes by. Also, after the article is published in the wiki, a notice is added to the page that says something to the effect that "this wiki page was the basis for the article published in the Geany newsletter of <date> under the title "<title>"".
It might be appropriate to do something like create an additional immutable page to serve as a permanent repository to the article, linked from the mutable page.
(I.e., the link in the newsletter points to a mutable page, the mutable page points to the original text published in the newsletter on an immutable page.)
Randy Kramer
Hi Randy,
I like Matthew's idea a lot, but I don't think what he described is quite like a teaser. It is more like the wiki becomes the canonical location for the information disclosed in the newsletter.
I also think that that was what he was suggesting, but I have some problems with that being an automatic situation.
When I say it that way, it is more like the newsletter is the teaser for the wiki, but I wouldn't suggest that either.
I just did , see other post :-) (not the whole newsletter of course, but some of it)
IMO, the newsletter should contain good, complete (i.e., self-contained) articles on some subject. The article should contain a link to a wiki page that is, at least at one point in time, the text of the article.
I don't really see the point of having the newsletter in nicely produced HTML, text, and PDF and wikified format as well. Using the wiki for developing the newsletter is noted below.
Potential newsletter articles might (well, I'd like to say should--there may be exceptions, perhaps due to deadline pressure) be posted on the wiki. Others can review those potential articles and make or suggest improvements in the wiki way.
The ability for newsletter content to be reviewed and commented by all and sundry is an absolute. The wiki may indeed be an effective tool for that as it lowers the bar for submission and especially comment and correction. I for one would probably do more if all I had to do was edit the wiki page because I only need a browser and can do it from any machine, rather than having to become a committer on the git repo or send in patches, but I think thats up to the production team.
But this use of the wiki as a tool for developing the newsletter should be clearly separate from the other information in the wiki because the development process is inevitably messy
(There might be a notice on the page saying either that the wiki page is proposed as a newsletter article (by the writer or someone else), or is anticipated to be (i.e., tentatively, at least, accepted as a newsletter article.)
This is part of the development process, see above.
When the article is published in the newsletter, there is a link to the wiki page.
Certainly any newsletter article should link to the wiki if it relates to something on the wiki, but just linking to its own content seems rather pointless.
Although having a comments page for each newsletter might be a good idea.
After the newsletter article is posted, the page remains on the wiki and (in the wiki way) is corrected and updated as time goes by. Also, after the article is published in the wiki, a notice is added to the page that says something to the effect that "this wiki page was the basis for the article published in the Geany newsletter of <date> under the title "<title>"".
Don't think leaving working drafts on the wiki is a good idea. If a topic is worthy of being in the wiki then it should be a wiki page properly categorised and tagged. This can of course evolve.
It might be appropriate to do something like create an additional immutable page to serve as a permanent repository to the article, linked from the mutable page.
As I said above, I don't see the point of keeping text, HTML, PDF and a wikified version of the newsletter.
Cheers Lex
Lex,
Hi!
On Sunday 05 June 2011 07:44:52 am Lex Trotman wrote:
Randy Kramer wrote:
IMO, the newsletter should contain good, complete (i.e., self-contained) articles on some subject. The article should contain a link to a wiki page that is, at least at one point in time, the text of the article.
I don't really see the point of having the newsletter in nicely produced HTML, text, and PDF and wikified format as well. Using the wiki for developing the newsletter is noted below.
Well, I'm not particularly advocating that the newsletter be kept in nicely produced HTML, text, and PDF and wikified format, but that might be the result of what I am advocating.
* IMHO, if a newsletter is published, a copy of it should be archived somewhere, sort of in an "as published" form, so that if somebody needs to see what was published, it can be found.
* I would like to see a wiki page used during the writing of each article to facilitate collaboration, etc.
* I'd like to see that same wiki page live on after the article is published as sort of the canonical source of the information that was used in the newsletter, but this should be a living thing. If circumstances change (patches to Geany to change behavior, whatever), the content of the wiki page should change accordingly.
As an example, if there is a newsletter article about, I don't know--setting margins (not that you'd do that in an editor), the article starts out on a wiki page. When it gets to be in good shape, or a publishing deadline arrives, it is dressed up and moved to the newsletter (or dressed up after being moved to the newsletter).
The newsletter gets published. The newsletter contains a link to the "source" wiki page, and the wiki page contains a link to the newsletter. (It might read: "An article, entitled <title> based on the content of this page as of <date> was published in the Geany Newsletter, dated <date>.")
Later a patch is added that changes the method of setting margins. The wiki page should get modified in the wiki way to reflect the new method. (The link to the newsletter might be changed to something like: "An article, entitled <title> based on the *previous* content of this page as of <date> was published in the Geany Newsletter, dated <date>."
Now, finally, the reason for the other wiki page that is immutable and contains the original text of the article: Suppose over the years, the content of that wiki page gets so changed that it is no longer recognizable as the source of the newsletter article?
Maybe the page just changes so much that it is unrecognizable. Or, it gets filled with so much content that it is decided to split the page into two or more pieces.
Somebody, reading an old copy of the newsletter (found on google), comes to that page from the newsletter and says "wtf" (pronounced double u, tee, eff)--this isn't what I'm looking for--something is wrong. At that point, the link to an immutable copy of the article would at least let the person know they came to what was the right page.
And, maybe, then they go back through the old revisions of the mutable page to see what happened.
Is that immutable page really useful? Well, it's the kind of thing I'd try to keep, but I'm probably in the minority.
regards, Randy Kramer
Potential newsletter articles might (well, I'd like to say should--there may be exceptions, perhaps due to deadline pressure) be posted on the wiki. Others can review those potential articles and make or suggest improvements in the wiki way.
The ability for newsletter content to be reviewed and commented by all and sundry is an absolute. The wiki may indeed be an effective tool for that as it lowers the bar for submission and especially comment and correction. I for one would probably do more if all I had to do was edit the wiki page because I only need a browser and can do it from any machine, rather than having to become a committer on the git repo or send in patches, but I think thats up to the production team.
But this use of the wiki as a tool for developing the newsletter should be clearly separate from the other information in the wiki because the development process is inevitably messy
(There might be a notice on the page saying either that the wiki page is proposed as a newsletter article (by the writer or someone else), or is anticipated to be (i.e., tentatively, at least, accepted as a newsletter article.)
This is part of the development process, see above.
When the article is published in the newsletter, there is a link to the wiki page.
Certainly any newsletter article should link to the wiki if it relates to something on the wiki, but just linking to its own content seems rather pointless.
Although having a comments page for each newsletter might be a good idea.
After the newsletter article is posted, the page remains on the wiki and (in the wiki way) is corrected and updated as time goes by. Also, after the article is published in the wiki, a notice is added to the page that says something to the effect that "this wiki page was the basis for the article published in the Geany newsletter of <date> under the title "<title>"".
Don't think leaving working drafts on the wiki is a good idea. If a topic is worthy of being in the wiki then it should be a wiki page properly categorised and tagged. This can of course evolve.
It might be appropriate to do something like create an additional immutable page to serve as a permanent repository to the article, linked from the mutable page.
As I said above, I don't see the point of keeping text, HTML, PDF and a wikified version of the newsletter.
* IMHO, if a newsletter is published, a copy of it should be archived somewhere, sort of in an "as published" form, so that if somebody needs to see what was published, it can be found.
Agree, it is, see http://wiki.geany.org/newsletter/start. And until Dominic broke it :-), an index of the newsletters was accessible from the website as well (see previous post).
* I would like to see a wiki page used during the writing of each article to facilitate collaboration, etc.
Yes I agree.
* I'd like to see that same wiki page live on after the article is published as sort of the canonical source of the information that was used in the newsletter, but this should be a living thing. If circumstances change (patches to Geany to change behavior, whatever), the content of the wiki page should change accordingly.
Now here we disagree, the newsletter itself should not be modifiable, its a snapshot in time.
Whilst there is stuff in the newsletter that merits a wiki page and needs to be maintained, there is stuff in the newsletter that doesn't merit a wiki page.
As an example, if there is a newsletter article about, I don't know--setting margins (not that you'd do that in an editor), the article starts out on a wiki page. When it gets to be in good shape, or a publishing deadline arrives, it is dressed up and moved to the newsletter (or dressed up after being moved to the newsletter).
Ok, the way I see it and I think the way others see it is that the wiki is the place for the details of operation and usage of Geany, the newsletter is not intended to contain detailed complex articles, it is intended to provide an overview of what is happening in the project, including referring to detailed howtos or other information added to the wiki, but also new features, plugins, human interest pieces on the developers etc. I'm not sure we want to spam the ML with huge detailed newsletters.
The newsletter gets published. The newsletter contains a link to the "source" wiki page, and the wiki page contains a link to the newsletter. (It might read: "An article, entitled <title> based on the content of this page as of <date> was published in the Geany Newsletter, dated <date>.")
Don't see the point of that, since even with your scheme the newsletter won't add anything to what the wiki says, and the wiki may be more up to date.
Later a patch is added that changes the method of setting margins. The wiki page should get modified in the wiki way to reflect the new method. (The link to the newsletter might be changed to something like: "An article, entitled <title> based on the *previous* content of this page as of <date> was published in the Geany Newsletter, dated <date>."
And thats just likely to be plain confusing :-)
Now, finally, the reason for the other wiki page that is immutable and contains the original text of the article: Suppose over the years, the content of that wiki page gets so changed that it is no longer recognizable as the source of the newsletter article?
So thats what the saved HTML, PDFand text newsletters are for.
Maybe the page just changes so much that it is unrecognizable. Or, it gets filled with so much content that it is decided to split the page into two or more pieces.
Thats the way wikis goes :-)
Somebody, reading an old copy of the newsletter (found on google), comes to that page from the newsletter and says "wtf" (pronounced double u, tee, eff)--this isn't what I'm looking for--something is wrong. At that point, the link to an immutable copy of the article would at least let the person know they came to what was the right page.
Whats the point of having an immutable wiki copy of the immutable newsletter both saying the same thing pointing to each other ... and both now wrong?
And, maybe, then they go back through the old revisions of the mutable page to see what happened.
How do they get there if the newsletter only points to the immutable copy?
The newsletter and the wiki are two separate entities with differing purposes, the newsletter is a snapshot of what is happening at a point in time, the wiki is a long term community gathered collection on wisdom? on Geany.
Cheers Lex
Do I understand you correct, that newsletter should work more as some kind of teaser for HowTo articles? Somehow I like that idea.
Hi Frank,
I don't think it was what Matthew was suggesting, but I do think that you have suggested a very valid function for the Newsletter, to remind people to look on the wiki with, as you put it, a teaser in the newsletter.
Popular sections like snippets or lists of tag files or large howto pages are not really suitable for the newsletter due to size, so teasers are a good idea.
Cheers Lex
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
On 6 June 2011 10:50, Matthew Brush mbrush@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.
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.
+1 Agree with all you said.
Cheers Lex
On Sunday 05 June 2011 10:42:41 pm Lex Trotman wrote:
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.
+1 Agree with all you said.
+1
Randy Kramer
On 6 June 2011 22:15, Randy Kramer rhkramer@gmail.com wrote:
On Sunday 05 June 2011 10:42:41 pm Lex Trotman wrote:
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.
+1 Agree with all you said.
+1
Randy Kramer
I'm amazed that (1) people understood what I wrote, (2) that two people agree with what I wrote.