Bored? Looking to kill some time? Want to chat with other SMF users? Join us in IRC chat or Discord
Started by Joshua Dickerson, November 28, 2010, 04:12:33 PM
Quote from: Daniel15 on November 30, 2010, 05:54:59 AMNice! I used to have a wiki for SMF modification developers, didn't renew the domain since I wasn't really keeping it alive and it kept getting spammed . I might have to go through the backups (I keep weekly backups of all my sites) and put some of the old articles up on this new wiki
Quote from: Dragooon on November 30, 2010, 09:02:24 AMJust a question, are you guys using the existing bridge between SMF and MediaWiki or have you guys developed one for you own or have you extended the one currently released?Can I sp4mz0rs the wikiz?
QuoteCan I ask, why did you choice MediaWiki? I seem to remember it being a big problem to decide which one to use simply because it was difficult to find one that was appropriate for our needs (especially language translations).
Quote[/size]Are there things like language filters on it? I would hope so, because there is never a time where any swear words would be needed in the documentation.
Quote[/size]I remember when we converted from our old wiki to using the SMF software because it was believed that SMF could be extensive enough to handle something like a documentation base. Do you feel like this is something that will now be forgotten, or should we someday see again an SMF install that can be modded to act as a wiki? Or maybe if/when an SM Core is released?
Quote[/size]How is version control being dealt with? This was the single biggest problem I had to handle. I don't see anything separating 1.1 from 2.0. Am I missing something or is it being worked on?
Quote from: akabugeyes on November 30, 2010, 03:50:39 PMAre there things like language filters on it? I would hope so, because there is never a time where any swear words would be needed in the documentation.
QuoteObviously you know of the other solutions as you and I discussed this before, but I really felt that going with something that was "easy" to setup and can easily be extended was the way to go
QuoteFor instance, when I was on the Customization Team, I announced that there will be an option for customization authors to create a wiki page for their customizations. That has been planned in this. With the current url structure, it will be easy for us to add other products, extensions, tools, and anything else we care to document
QuoteAs has been said before, if people create or modify pages with changes that we don't agree with, we'll revert them. If people continue to go along that route, they'll be banned. At the start, they'll not be able to make changes to the wiki and probably have some kind of ban from the forum. If you are a problem on one part of the site, we don't want you to continue that behavior elsewhere. I do like your suggestion of some kind of filter though. I will research that and you may see it added in the future.
QuoteA wiki, not just Mediawiki was chosen over SMF because it is the right tool for the job. We could use a wrench to hammer nails, but a hammer would work better for the job. I've selected "user driven education" as our motto for a reason. We, the team, shouldn't be doing all of the work. Especially when there are plenty of willing and capable people to help. I'd like for us to lead the masses and moderate where needed, but we aren't capable of doing it all. I have a vision of having a near autonomous (from the team) website where we here to develop the system which runs the website and ensure that things run smoothly. Other than that, the software can handle most of what happens around here. Especially when it comes to support (support and documentation to me are one in the same).
QuoteSMF 1.1 will be supported by the old Online Manual. I plan to convert it to something more static (searching will still be available) and at some point far down the line it will probably be dropped altogether. Future versions of SMF can be done with our current URL structure. Although, I have some other possibilities - looking at how MySQL does their documentation. You'll see on some pages that 1.1 documentation has found its way to the wiki. There are headings separating SMF 1.1 and SMF 2.0.