[wiki - new howto] How to setup PostfixAdmin
https://trac.macports.org/wiki/howto/PostfixAdmin comments are welcome :-) -- Bjarne D Mathiesen København N ; Danmark ; Europa -- denne besked er skrevet i et totalt M$-frit miljø MacOS X 10.6.7 Snow Leopard ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 http://webadmin.mathiesen.info/ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: [wiki - new howto] How to setup MySQL Workbench to work with MacPorts
https://trac.macports.org/wiki/howto/MySQLWorkbench OK - I'll do the following then : 1) annotate the pictures 2) reduce them i size 3) add text describing what's happening My schedule for this will be that I'll do one picture a day from the coming Monday ... I'm busy with other stuff over the weekend :-) I'm still experimenting with postfix, postfixadmin et alia -- Bjarne D Mathiesen København N ; Danmark ; Europa -- denne besked er skrevet i et totalt M$-frit miljø MacOS X 10.6.7 Snow Leopard ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 http://webadmin.mathiesen.info/ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
[wiki - new howto] How to setup MySQL Workbench to work with MacPorts
https://trac.macports.org/wiki/howto/MySQLWorkbench I've done the preliminaries on a new howto ! TODO: +1: add comments +2: modify the illustrations with pointers reflecting the comments +3: add information in how to modify permissions on individual schemas and tables on a user-by-user basis Question: +1: should I reduce the size of the individual images ? and by how much ? Problem: +1: I inadvertently uploaded the same image twice :-( how do I remove the duplicate ? At this point in time I'ld like to solicit your comments on the howto ! Feel free to give me the once-over .-) -- Bjarne D Mathiesen København N ; Danmark ; Europa -- denne besked er skrevet i et totalt M$-frit miljø MacOS X 10.6.7 Snow Leopard ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 http://webadmin.mathiesen.info/ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: [wiki - new howto] How to setup MySQL Workbench to work with MacPorts
On Jun 23, 2011, at 04:34, Bjarne D Mathiesen wrote: https://trac.macports.org/wiki/howto/MySQLWorkbench +1: should I reduce the size of the individual images ? and by how much ? They are perhaps a bit large as is. Maybe a 20% reduction wouldn't affect readability too much? You can play around with it, I don't think we have any guidelines since we haven't really gotten into creating guides with screenshots yet, though it can be quite helpful for new users so thank you for working on it. +1: I inadvertently uploaded the same image twice :-( how do I remove the duplicate ? I am not certain if regular users can delete attachments from Trac, but I have deleted the duplicate attachment for you. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: [wiki - new howto] How to setup MySQL Workbench to work with MacPorts
On Jun 23, 2011, at 1:08 PM, Ryan Schmidt wrote: On Jun 23, 2011, at 04:34, Bjarne D Mathiesen wrote: https://trac.macports.org/wiki/howto/MySQLWorkbench +1: should I reduce the size of the individual images ? and by how much ? They are perhaps a bit large as is. Maybe a 20% reduction wouldn't affect readability too much? You can play around with it, I don't think we have any guidelines since we haven't really gotten into creating guides with screenshots yet, though it can be quite helpful for new users so thank you for working on it Hear, hear. Thank you for contributing Bjarne. I have been spending time packaging up some private stuff I have been running in the hopes of riding your documentation wave. postfix+virtual-mysql+dspam+sqlgrey+dovecot+dovecot-sieve+dovecot-managesieve+roundcube+roundcube-sieverules-plugin Regards, Bradley Giesbrecht (pixilla) ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
New Wiki (Was: New Howto)
Hi, I would say, if I had a vote (who does?), that whatever people are willing to use wins. It may not be elegant or state of the art, but the best is the enemy of the good, and good is usually good enough. I like to point out one more aspect: *If* we are going for a new Wiki we might as well replace the homepage as well. For a week or so there was consensus (as in: no one disagreed) that a link from the homepage to the HowTo would be helpful - yet it has not been done. Let me check No still not done. And we would not be the first project to go all wiki: http://gnuada.sourceforge.net/ http://uiq3.sourceforge.net/wiki/index.php/Main_Page http://vimplugin.org/ Martin ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
Zitat von Jordan K. Hubbard [EMAIL PROTECTED]: Well, to be fair, I thought I was trying to address that by suggesting that there should be a top level doc project - individual projects could point up to it just as easily as it could point down to them, but it would be a clear docs portal for everyone. Note that MediaWiki supports up to 256 name spaces. For example on wikibooks the cookbook runs in it's own name space: http://en.wikibooks.org/wiki/Cookbook I think it would be a good idea to have one wiki for - including the homepage. It just need a clear structure form the onset. Martin ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Wiki (Was: New Howto)
On Jun 11, 2008, at 01:15, Martin Krischik wrote: I would say, if I had a vote (who does?), that whatever people are willing to use wins. It may not be elegant or state of the art, but the best is the enemy of the good, and good is usually good enough. I like to point out one more aspect: *If* we are going for a new Wiki we might as well replace the homepage as well. For a week or so there was consensus (as in: no one disagreed) that a link from the homepage to the HowTo would be helpful - yet it has not been done. Let me check No still not done. And we would not be the first project to go all wiki: http://gnuada.sourceforge.net/ http://uiq3.sourceforge.net/wiki/index.php/Main_Page http://vimplugin.org/ The proposed new wiki was to be a global Mac OS Forge documentation wiki, not a MacPorts-specific wiki. I'm still not a fan of the idea. Do we really want to spend the time and energy converting content from the MacPorts Trac wiki to a Mac OS Forge MediaWiki when we have more important things we could be doing? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Wiki (Was: New Howto)
Zitat von Ryan Schmidt [EMAIL PROTECTED]: On Jun 11, 2008, at 01:15, Martin Krischik wrote: I would say, if I had a vote (who does?), that whatever people are willing to use wins. It may not be elegant or state of the art, but the best is the enemy of the good, and good is usually good enough. I like to point out one more aspect: *If* we are going for a new Wiki we might as well replace the homepage as well. For a week or so there was consensus (as in: no one disagreed) that a link from the homepage to the HowTo would be helpful - yet it has not been done. Let me check No still not done. And we would not be the first project to go all wiki: http://gnuada.sourceforge.net/ http://uiq3.sourceforge.net/wiki/index.php/Main_Page http://vimplugin.org/ The proposed new wiki was to be a global Mac OS Forge documentation wiki, not a MacPorts-specific wiki. I'm still not a fan of the idea. Do we really want to spend the time and energy converting content from the MacPorts Trac wiki to a Mac OS Forge MediaWiki when we have more important things we could be doing? I don't know either - but if we do I propose we replace the home pages (and macports guide) as well. Note that a quick check shows that Bonjour, BridgeSupport, CalendarServer, MacRuby etc. use the track wiki as home page. *If* we go thue the trouble of installing media wiki - or any other large scale wiki - then we might as well use it for the homepage and the guide as well. But note the *if* - maybe the track wiki is enough after all - in which case I suggest we move at least the guide to track wiki as well to have more in one place. From my quick check I also noted that MacPorts clearly is the largest Project on MacOS Forge ao we might as well take the lead. Martin ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Wiki (Was: New Howto)
On Wed, Jun 11, 2008 at 4:18 AM, Martin Krischik [EMAIL PROTECTED] wrote: Zitat von Ryan Schmidt [EMAIL PROTECTED]: On Jun 11, 2008, at 01:15, Martin Krischik wrote: I would say, if I had a vote (who does?), that whatever people are willing to use wins. It may not be elegant or state of the art, but the best is the enemy of the good, and good is usually good enough. I like to point out one more aspect: *If* we are going for a new Wiki we might as well replace the homepage as well. For a week or so there was consensus (as in: no one disagreed) that a link from the homepage to the HowTo would be helpful - yet it has not been done. Let me check No still not done. And we would not be the first project to go all wiki: http://gnuada.sourceforge.net/ http://uiq3.sourceforge.net/wiki/index.php/Main_Page http://vimplugin.org/ I don't know of any large project to go all wiki. Even wikimedia/wikipedia has locked down much of its wiki in the same way that www.macports.org is locked down against random edits of anyone. The proposed new wiki was to be a global Mac OS Forge documentation wiki, not a MacPorts-specific wiki. I'm still not a fan of the idea. Do we really want to spend the time and energy converting content from the MacPorts Trac wiki to a Mac OS Forge MediaWiki when we have more important things we could be doing? Does anyone remember when MacPorts and Fink used the same mediawiki instance for their wiki? Namespaces, interlinking, and searches were fun as one project would get the nice page name or search results would kick you from one project to the other...it was not nice, to say the least. I don't know either - but if we do I propose we replace the home pages (and macports guide) as well. We should not replace these. We can improve them and change the workflow that controls them, but I do not like the idea of replacing (relatively) static and controlled information sources with a completely open one. Note that a quick check shows that Bonjour, BridgeSupport, CalendarServer, MacRuby etc. use the track wiki as home page. *If* we go thue the trouble of installing media wiki - or any other large scale wiki - then we might as well use it for the homepage and the guide as well. But note the *if* - maybe the track wiki is enough after all - in which case I suggest we move at least the guide to track wiki as well to have more in one place. The trac wiki has a couple of major advantages over other wikis, particularly for our project: integrated ticketing and svn browsing. If we cut off part of trac, we need to loose it all, and that means also standing up bugzilla, and using viewcvs (which is just ugly after trac) and none of these are integrated, and ...wait... we've returned to the old opendarwin.org infrastructure, and all of its maintenance headaches (it was essentially abandoned because of the amount of maintenance work involved). From my quick check I also noted that MacPorts clearly is the largest Project on MacOS Forge ao we might as well take the lead. Martin ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -- Randall Wood [EMAIL PROTECTED] The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
On Jun 10, 2008, at 11:23 PM, Martin Krischik wrote: Note that MediaWiki supports up to 256 name spaces. For example on wikibooks the cookbook runs in it's own name space: http://en.wikibooks.org/wiki/Cookbook I think it would be a good idea to have one wiki for - including the homepage. It just need a clear structure form the onset. That's a bit more ambitious than what I had in mind, at least at the very start, but I think that's a fine goal. Why don't we do this: Why don't we get MediaWiki up on the MacOSForge cluster and start experimenting with it? If we don't like it, we certainly don't have to use it, but we should have options. I've used trac to edit various things on MacOSForge and cannot consider myself a fan of it given how it makes a number of things which should be simple and obvious, well, rather less so. I've also added entries to wikipedia, or edited existing ones, and found that to be a very straight-forward and relatively intuitive process by comparison. - Jordan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Wiki (Was: New Howto)
On Jun 10, 2008, at 11:32 PM, Ryan Schmidt wrote: The proposed new wiki was to be a global Mac OS Forge documentation wiki, not a MacPorts-specific wiki. I'm still not a fan of the idea. Do we really want to spend the time and energy converting content from the MacPorts Trac wiki to a Mac OS Forge MediaWiki when we have more important things we could be doing? I think that's something of a straw man argument, Ryan. First off, if the conversion chore is genuinely distasteful then you can always elect not to do it but simply point others who ARE willing at your raw material and say if you want to pretty that up and convert it, be our guest! If the end result ends up looking a lot nicer, or is easier to find, you then simply change which one is now live and deprecate the other, either quickly or over time. Second, there just aren't that many howtos right now, at least not in comparison to what could be, and if there's a time to bear any conversion cost then that time is now, not later after there are dozens of the things. I think a simple evaluation, as I just proposed to Martin, is a reasonable next step at this point. How are you sure you're using the best tool for the job if you haven't even tried other alternatives? - Jordan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Wiki (Was: New Howto)
On Jun 11, 2008, at 1:18 AM, Martin Krischik wrote: From my quick check I also noted that MacPorts clearly is the largest Project on MacOS Forge ao we might as well take the lead. Actually, I believe that honor goes to WebKit. :-) It would be nice to have some pageview stats to back that up, of course. I'll see about some sort of macosforge-wide project status page. - Jordan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Fwd: New Howto
Failed to send to list... -- Forwarded message -- From: Randall Wood [EMAIL PROTECTED] Date: Wed, Jun 11, 2008 at 2:55 PM Subject: Re: New Howto To: Jordan K. Hubbard [EMAIL PROTECTED] On Wed, Jun 11, 2008 at 2:02 PM, Jordan K. Hubbard [EMAIL PROTECTED] wrote: On Jun 10, 2008, at 11:23 PM, Martin Krischik wrote: Note that MediaWiki supports up to 256 name spaces. For example on wikibooks the cookbook runs in it's own name space: http://en.wikibooks.org/wiki/Cookbook I think it would be a good idea to have one wiki for - including the homepage. It just need a clear structure form the onset. That's a bit more ambitious than what I had in mind, at least at the very start, but I think that's a fine goal. Why don't we do this: Why don't we get MediaWiki up on the MacOSForge cluster and start experimenting with it? If we don't like it, we certainly don't have to use it, but we should have options. I've used trac to edit various things on MacOSForge and cannot consider myself a fan of it given how it makes a number of things which should be simple and obvious, well, rather less so. I've also added entries to wikipedia, or edited existing ones, and found that to be a very straight-forward and relatively intuitive process by comparison. I'll ask this instead: Why not simply get our trac site looking like we want it, instead of having it in the hideous MacOSForge theme? Webkit is using the MacOSForge trac without all the MacOSForge stuff on it and with its own theme. We could do the same thing. I'm not aware that we have tried. I'll also give you a reason not to stand up MediaWiki on MacOSForge: It will lead to multiple wiki syntaxes in MacPorts unless we abandon trac for SVN browsing and ticketing. And I really don't want to see that. viewcvs sucks as an SVN browsers, and MediaWiki/Bugzilla/SVN have no real integration between each other. We'll loose the integration that trac brings and it is valuable. - Jordan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -- Randall Wood [EMAIL PROTECTED] The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy. -- Randall Wood [EMAIL PROTECTED] The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
Leaving aside the issue of what the best platform for sharing the info might be. If nobody knows it's there, the kick-assingest wiki server the world has or will ever see is not going to address my suggestion in the slightest. My point was that it's quite a challenge finding the current how-to's even if you already know they exist. If you are not in that smallish (I'm guessing--but I've been using *Ports for a fairly long time, and it was a recent message on this list that made me aware) category, then the chances this very useful series of articles will reach the audience that needs it is quite small. Just to refresh, there needs to be a link from the main MacPorts documentation site to the how-to's. As a first step, it's awesome. On Thu, Jun 5, 2008 at 2:22 PM, Jordan K. Hubbard [EMAIL PROTECTED] wrote: On Jun 5, 2008, at 8:42 AM, Lorin Rivers wrote: Awesome! I did not even know about these How To's. You know, it's actually kind of hard to find them, if you don't know about where they are in the first place. I think they deserve more prominence. There should be a link from the documentation area of the main MacPorts site to the HowTo's. I'm still of the opinion that we should install mediawiki on the site and turn these howtos into full-blown, collaboratively maintained reference pages worthy of wikipedia (but, unlike wikipedia, also free to be relevant only in the context of projects hosted at macosforge). What do other folks think? - Jordan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
On Tue, Jun 10, 2008 at 12:00 PM, [EMAIL PROTECTED] wrote: Message: 11 Date: Tue, 10 Jun 2008 11:27:30 -0500 From: Lorin Rivers [EMAIL PROTECTED] Subject: Re: New Howto To: Jordan K. Hubbard [EMAIL PROTECTED] Cc: MacPorts Users macports-users@lists.macosforge.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=utf-8 Leaving aside the issue of what the best platform for sharing the info might be. If nobody knows it's there, the kick-assingest wiki server the world has or will ever see is not going to address my suggestion in the slightest. My point was that it's quite a challenge finding the current how-to's even if you already know they exist. If you are not in that smallish (I'm guessing--but I've been using *Ports for a fairly long time, and it was a recent message on this list that made me aware) category, then the chances this very useful series of articles will reach the audience that needs it is quite small. Just to refresh, there needs to be a link from the main MacPorts documentation site to the how-to's. As a first step, it's awesome. Taking up the earlier comment on a need for discussion, what are the pros and cons of the different wiki platforms? I would say, if I had a vote (who does?), that whatever people are willing to use wins. It may not be elegant or state of the art, but the best is the enemy of the good, and good is usually good enough. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
On Jun 10, 2008, at 9:27 AM, Lorin Rivers wrote: Leaving aside the issue of what the best platform for sharing the info might be. If nobody knows it's there, the kick-assingest wiki server the world has or will ever see is not going to address my suggestion in the slightest. Well, to be fair, I thought I was trying to address that by suggesting that there should be a top level doc project - individual projects could point up to it just as easily as it could point down to them, but it would be a clear docs portal for everyone. I know not everyone agrees with this assertion, but I think all the projects on macosforge have more knowledge collectively in common than they think. I then look laterally to the success of projects like wikipedia, which has a knowledge base and contributing community far more vast by comparison, and cannot help but think hmmm.. Just to refresh, there needs to be a link from the main MacPorts documentation site to the how-to's. As a first step, it's awesome. No disagreement at all. Links are cheap, people! Use them! - Jordan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
On Jun 6, 2008, at 21:20, paul beard wrote: On Fri, Jun 6, 2008 at 12:00 PM, wrote: We should not now add another wiki system with a conflicting syntax. If we wanted to switch from Trac wiki to MediaWiki we could discuss that, but converting all existing content could be difficult (though maybe someone's already written an importer; I haven't looked). Do we have to discuss it? I think discussion is one of the reasons there is no 1.6.x release (or an even more full-featured one). What format are most of the articles in and what flavor is getting the most attention right now? And who decided a format as simple as wiki needed to be forked or otherwise complicated? The MacPorts project is not a dictatorship, it's an open-source collaborative project, and mine is not the only opinion, hence discussion. My opinion is we should not have two wiki systems with different syntax rules. We have enough trouble getting people to follow just the syntax rules for Trac today. (Bugs are constantly filed with wrong syntax.) We should either keep Trac as the only wiki system, or move to MediaWiki as the only wiki system, and convert all existing content to MediaWiki format, and close the Trac wiki. The former option is less work so I vote for that, since I haven't seen any outcry against the Trac wiki. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
On 6/5/08, Jordan K. Hubbard [EMAIL PROTECTED] wrote: On Jun 5, 2008, at 8:42 AM, Lorin Rivers wrote: Awesome! I did not even know about these How To's. You know, it's actually kind of hard to find them, if you don't know about where they are in the first place. I think they deserve more prominence. There should be a link from the documentation area of the main MacPorts site to the HowTo's. I'm still of the opinion that we should install mediawiki on the site and turn these howtos into full-blown, collaboratively maintained reference pages worthy of wikipedia (but, unlike wikipedia, also free to be relevant only in the context of projects hosted at macosforge). What do other folks think? A fantastic idea! And MediaWiki is itself a MacPort. Very cool! Tabitha - Jordan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
On 6/5/08, Tabitha McNerney [EMAIL PROTECTED] wrote: On 6/5/08, Jordan K. Hubbard [EMAIL PROTECTED] wrote: On Jun 5, 2008, at 8:42 AM, Lorin Rivers wrote: Awesome! I did not even know about these How To's. You know, it's actually kind of hard to find them, if you don't know about where they are in the first place. I think they deserve more prominence. There should be a link from the documentation area of the main MacPorts site to the HowTo's. I'm still of the opinion that we should install mediawiki on the site and turn these howtos into full-blown, collaboratively maintained reference pages worthy of wikipedia (but, unlike wikipedia, also free to be relevant only in the context of projects hosted at macosforge). What do other folks think? A fantastic idea! And MediaWiki is itself a MacPort. Very cool! An update after I read the rest of the thread ... if I recall, MacPorts.org is graciously hosted on servers provided by Apple true? Xserve? MacPro tower? If so, then what about the software -- is it Mac OS X Server or Mac OS X? If OS X Server, is it Leopard? If so, could we then avail of Apple's built-in-to-Leopard-Server Wiki? Just another thought. Thanks, T.M. Tabitha - Jordan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
On 6/5/08 8:32 PM, Jordan K. Hubbard [EMAIL PROTECTED] wrote: On Jun 5, 2008, at 4:58 PM, Rainer Müller wrote: We already have spread our website over enough different places. There is macports.org http://macports.org , trac.macports.org http://trac.macports.org and guide.macports.org http://guide.macports.org (and the upcoming MPWA at db.macports.org http://db.macports.org ). It is already hard enough to find the relevant information one is looking for. If we now add yet another new site, this will become even worse. Rainer, I'm beginning to wonder if you just like to argue. I know, the thought of a german who likes to argue - it's almost impossible to conceive of, isn't it? :-) I was thinking of a somewhat broader problem space than just MacPorts here, given that the notion of writing howtos ultimately and logically extends well beyond just the software you choose to add explicitly yourself. There are also other projects on macosforge who would like to see their own howtos on various topics, some of which are essentially meta-topics (you must know foo before you can understand bar, even though foo is not logically in the domain of what we are doing). Rather than have multiple people re-write howtos like The Unix PATH and how it affects you, it would therefore be better to have a group of documentation-centric people who maintain howtos (or mediawiki pages) like that, whether or not they're also members of the macports project (or the ruby project or the webkit project) being essentially irrelevant as long as they can write good docs. There's no rule that says all developers have to be in one and only one project, or that all projects have to force all URLs into a single domain in order for people to find stuff. From my perspective, knowing I can go to http://howto.macosforge.org or http://doc.macosforge.org, or whatever the heck we might decide to call it, and find all the docs that the various projects are publishing seems to make it a lot EASIER to find the information I am looking for rather than the opposite. More to the point, if we feel it's appropriate to have a general documentation project on MacOSForge, we're going to create one regardless of what macports decides to do since we have plenty of meta-topics to cover, including but not limited to general rules of the road for open source collaboration, how to use MacOSForge itself, etc etc. In comparison with that, splintering the docs into different domains and documentation formats seems a lot more confusing to me as well as having the potential to turn away contributors who would like to write end-user tutorials on using popular software but don't actually use macports. What's been done in macports so far represents an excellent start, don't get me wrong, but it's also raising the question as to whether or not it's happening in precisely the right project context and/or using the right tools. In any case, there's little point in arguing about this since the bigger picture goal here is going to evolve independently of any argument you or I might have anyway, so I think both you and I can save our fingerpads this time around. Jordan, I was pleasantly surprised to see you on the list as I remember you way back from my FreeBSD list days. Anyways I think what needs to happen first is to decide what should be MacOSForge and what should be MacPorts and split the documentation appropriately. Maybe restrict the documentation on MacPorts to just the documentation on how to use MacPorts, how to develop ports for MacPorts and how to troubleshoot repair a broken MacPorts tree and put the appropriate OSS project how-tos under MacOSForge. You can always create out-of-wiki links between the two. It's probably not the most thought out approach but my wife is talking my ear off while I write this... -Ross ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
Awesome! I did not even know about these How To's. You know, it's actually kind of hard to find them, if you don't know about where they are in the first place. I think they deserve more prominence. There should be a link from the documentation area of the main MacPorts site to the HowTo's. On Mon, Jun 2, 2008 at 1:11 PM, Martin Krischik [EMAIL PROTECTED] wrote: Hello, just wanted to let you know that I finished a new Howto http://trac.macports.org/wiki/howto/SetupDovecot It's the first of a 3 part series and I hope finish the other parts soon. Martin ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
On Jun 5, 2008, at 8:42 AM, Lorin Rivers wrote: Awesome! I did not even know about these How To's. You know, it's actually kind of hard to find them, if you don't know about where they are in the first place. I think they deserve more prominence. There should be a link from the documentation area of the main MacPorts site to the HowTo's. I'm still of the opinion that we should install mediawiki on the site and turn these howtos into full-blown, collaboratively maintained reference pages worthy of wikipedia (but, unlike wikipedia, also free to be relevant only in the context of projects hosted at macosforge). What do other folks think? - Jordan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
Simple pages where you can read what to do and then do them are VERY GOOD. I like simple and straightforwards. Also, how to recover from errors are very good. I plan on having virgin OS X installs set up to make sure these HowTos work from a new install. - Zav On Jun 5, 2008, at 2:22 PM, Jordan K. Hubbard wrote: On Jun 5, 2008, at 8:42 AM, Lorin Rivers wrote: Awesome! I did not even know about these How To's. You know, it's actually kind of hard to find them, if you don't know about where they are in the first place. I think they deserve more prominence. There should be a link from the documentation area of the main MacPorts site to the HowTo's. I'm still of the opinion that we should install mediawiki on the site and turn these howtos into full-blown, collaboratively maintained reference pages worthy of wikipedia (but, unlike wikipedia, also free to be relevant only in the context of projects hosted at macosforge). What do other folks think? - Jordan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 05.06.2008 um 21:22 schrieb Jordan K. Hubbard: On Jun 5, 2008, at 8:42 AM, Lorin Rivers wrote: Awesome! I did not even know about these How To's. You know, it's actually kind of hard to find them, if you don't know about where they are in the first place. I think they deserve more prominence. There should be a link from the documentation area of the main MacPorts site to the HowTo's. I'm still of the opinion that we should install mediawiki on the site and turn these howtos into full-blown, collaboratively maintained reference pages worthy of wikipedia (but, unlike wikipedia, also free to be relevant only in the context of projects hosted at macosforge). What do other folks think? Well I am quite happy with the wiki as it is - anybody can register and edit. No Problem here. Note that fully open Wikis need SPAM protection which can be tricky so the need to register is quite ok for a small Wiki. What we need is an easier to find link off the main page! Regards Martin -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iD8DBQFISEH1ijwKaHyem9cRAvXyAJ0dPqAI/t5i4xSpk7l1MKPPr9J31ACfeJo1 iyiz4lXU59wLU6F+5L1Vp4o= =lG95 -END PGP SIGNATURE- ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
Jordan K. Hubbard wrote: I'm still of the opinion that we should install mediawiki on the site and turn these howtos into full-blown, collaboratively maintained reference pages worthy of wikipedia (but, unlike wikipedia, also free to be relevant only in the context of projects hosted at macosforge). What do other folks think? We already have spread our website over enough different places. There is macports.org, trac.macports.org and guide.macports.org (and the upcoming MPWA at db.macports.org). It is already hard enough to find the relevant information one is looking for. If we now add yet another new site, this will become even worse. I don't see what a MediaWiki would offer that a Trac Wiki does not. Okay, Trac Wiki has some caveats (like it does not do automatic merging when editing simultaneously). But I don't see a major benefit from switching to MediaWiki. We already opened up the wiki access to anyone who registers, so I think that's collaborative enough. Rainer ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
On Jun 5, 2008, at 4:58 PM, Rainer Müller wrote: We already have spread our website over enough different places. There is macports.org, trac.macports.org and guide.macports.org (and the upcoming MPWA at db.macports.org). It is already hard enough to find the relevant information one is looking for. If we now add yet another new site, this will become even worse. Rainer, I'm beginning to wonder if you just like to argue. I know, the thought of a german who likes to argue - it's almost impossible to conceive of, isn't it? :-) I was thinking of a somewhat broader problem space than just MacPorts here, given that the notion of writing howtos ultimately and logically extends well beyond just the software you choose to add explicitly yourself. There are also other projects on macosforge who would like to see their own howtos on various topics, some of which are essentially meta-topics (you must know foo before you can understand bar, even though foo is not logically in the domain of what we are doing). Rather than have multiple people re-write howtos like The Unix PATH and how it affects you, it would therefore be better to have a group of documentation-centric people who maintain howtos (or mediawiki pages) like that, whether or not they're also members of the macports project (or the ruby project or the webkit project) being essentially irrelevant as long as they can write good docs. There's no rule that says all developers have to be in one and only one project, or that all projects have to force all URLs into a single domain in order for people to find stuff. From my perspective, knowing I can go to http://howto.macosforge.org or http://doc.macosforge.org, or whatever the heck we might decide to call it, and find all the docs that the various projects are publishing seems to make it a lot EASIER to find the information I am looking for rather than the opposite. More to the point, if we feel it's appropriate to have a general documentation project on MacOSForge, we're going to create one regardless of what macports decides to do since we have plenty of meta- topics to cover, including but not limited to general rules of the road for open source collaboration, how to use MacOSForge itself, etc etc. In comparison with that, splintering the docs into different domains and documentation formats seems a lot more confusing to me as well as having the potential to turn away contributors who would like to write end-user tutorials on using popular software but don't actually use macports. What's been done in macports so far represents an excellent start, don't get me wrong, but it's also raising the question as to whether or not it's happening in precisely the right project context and/or using the right tools. In any case, there's little point in arguing about this since the bigger picture goal here is going to evolve independently of any argument you or I might have anyway, so I think both you and I can save our fingerpads this time around. - Jordan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
On Jun 5, 2008, at 19:32, Jordan K. Hubbard wrote: On Jun 5, 2008, at 4:58 PM, Rainer Müller wrote: We already have spread our website over enough different places. There is macports.org, trac.macports.org and guide.macports.org (and the upcoming MPWA at db.macports.org). It is already hard enough to find the relevant information one is looking for. If we now add yet another new site, this will become even worse. Rainer, I'm beginning to wonder if you just like to argue. I know, the thought of a german who likes to argue - it's almost impossible to conceive of, isn't it? :-) I was going to disagree with you too, Jordan. Then again, I'm German too... Hmm... :-) I was thinking of a somewhat broader problem space than just MacPorts here, given that the notion of writing howtos ultimately and logically extends well beyond just the software you choose to add explicitly yourself. There are also other projects on macosforge who would like to see their own howtos on various topics, some of which are essentially meta-topics (you must know foo before you can understand bar, even though foo is not logically in the domain of what we are doing). Rather than have multiple people re-write howtos like The Unix PATH and how it affects you, it would therefore be better to have a group of documentation- centric people who maintain howtos (or mediawiki pages) like that, whether or not they're also members of the macports project (or the ruby project or the webkit project) being essentially irrelevant as long as they can write good docs. There's no rule that says all developers have to be in one and only one project, or that all projects have to force all URLs into a single domain in order for people to find stuff. From my perspective, knowing I can go to http://howto.macosforge.org or http://doc.macosforge.org, or whatever the heck we might decide to call it, and find all the docs that the various projects are publishing seems to make it a lot EASIER to find the information I am looking for rather than the opposite. More to the point, if we feel it's appropriate to have a general documentation project on MacOSForge, we're going to create one regardless of what macports decides to do since we have plenty of meta-topics to cover, including but not limited to general rules of the road for open source collaboration, how to use MacOSForge itself, etc etc. In comparison with that, splintering the docs into different domains and documentation formats seems a lot more confusing to me as well as having the potential to turn away contributors who would like to write end-user tutorials on using popular software but don't actually use macports. What's been done in macports so far represents an excellent start, don't get me wrong, but it's also raising the question as to whether or not it's happening in precisely the right project context and/or using the right tools. Ah, I didn't understand at all from your original post that you were thinking of a larger scope than MacPorts, so thanks for clarifying that. Still, I like that we have documentation on how to set up the PATH for MacPorts, not just a general document on the PATH that lacks MacPorts specifics. And I like that we're getting how-tos which tell you how to do things with MacPorts that people frequently ask how to do. I think MediaWiki is a fine wiki engine. It's the wiki system I use for myself personally. At the time I set that up, I liked its wiki syntax best. But I think a more important consideration is that we already have a wiki system in Trac. We should not now add another wiki system with a conflicting syntax. If we wanted to switch from Trac wiki to MediaWiki we could discuss that, but converting all existing content could be difficult (though maybe someone's already written an importer; I haven't looked). I'm in fact in favor of separating MacPorts further from Mac OS Forge, not joining it further by creating a consolidated documentation space. For example, I'd like to get the links to the other Mac OS Forge hosted projects off of the MacPorts Trac web pages; IMHO they have no place there. As a MacPorts user, I really don't need to know that Mac OS Forge also hosts Bonjour, BridgeSupport, CalendarServer, etc.; If I want to know that I can go to www.macosforge.org. In any case, there's little point in arguing about this since the bigger picture goal here is going to evolve independently of any argument you or I might have anyway, so I think both you and I can save our fingerpads this time around. Oh. Right. :-) ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
New Howto
Hello, just wanted to let you know that I finished a new Howto http://trac.macports.org/wiki/howto/SetupDovecot It's the first of a 3 part series and I hope finish the other parts soon. Martin ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
