What are the cons for a github-hosted wiki again? It really seems to make sense to have all of the source and the how-to hosted in one place, in an easy to use and modify format. Admin and source control is easy to use (it is designed for it, after all), managed, and attached to the repo for owfs itself. This really seems like the obvious solution to me.
https://help.github.com/articles/about-github-wikis/ Colin On 9/7/2016 3:03 PM, Jan Kandziora wrote: > Am 07.09.2016 um 21:23 schrieb Johan Ström: >> >> Pro: >> - would be able to properly version it in git >> - Could integrate with automatic build on push, using pull requests for >> contribution etc. >> - static is simple >> Cons: >> - Depending on how it's implemented, it could be trickier to contribute. >> But most contributors are probably somewhat tech-savvy anyway.. >> > If we use "simple" markup, we have to pick a person who extends the > "simple" markup as needed. I don't like the idea of not being able to > draw a table in a certain way or arrange text around an image just > because the "simple" markup does not support what I need. > > In reality, we don't need this "simple" markup when all the people who > are contributing to the documentation are developers. > > It's either user+developers, then cms/wiki is the way to go, or plain > old html files, with some preprocessing to put each article into a > common frame, suppling breadcrumbs and a table of contents > automatically. All inbetween will gives us a headache. > > >> >> I'm going to lift a followup question: should we stay on sourceforge? >> Even if Github may be hyped and nowadays used by every granny and her >> cat, it *is* a lot better than Sourceforge when it comes to git.. and >> everything around it.. >> We would certainly not be the first project to leave SF.. They may not >> yet have covertly bundled installers and what not with owfs, but who >> knows.. >> (http://www.infoworld.com/article/2931753/open-source-software/sourceforge-the-end-cant-come-too-soon.html). >> > I have some old projects at sourceforge but yes, I've started new > projects on github only since some years ago. I would never again begin > a new project on sf.net. > > Why? Because sf.net is the yahoo of software. Totally bloated and full > of bells and whistles you don't want, with the main functions > complicated and brittle. > > > >> I haven't looked at github pages much more than during writing message, >> but something like this is tempting: >> * Move project to github: git hosting, issue handling, pull requests. >> * Setup new github pages, automatically built by pushing to either main >> repo or a separate site repo. If we juse sphinx, jekyll, or plain >> markdown, or something else, I don't know. >> * Handle contributions to docs and source the same way: pull requests >> >> Github could thus handle: GIT, basic descriptions, issues, pull >> requests, pages (site), releases. >> However, not mailinglist. We could keep that at sourceforge though. >> > I would like to consolidate the ways to report problems and bugs. It's a > bit tedious to have this at so many locations. Sourceforge does a > terrible job translating between the different interfaces. > > Any good plan how to migrate this? What should the mailing list be good > for in the future? Developers only? If yes, who is taking care for > people reporting problems and bugs on the github tracker? > > >> (as it happens, I just created https://github.com/owfs. If we're not >> going to use it, then at least so no-one else can steal it.. :)) >> > Fine. Please add me (ianka) to the organisation. > > >>> If we had to rewrite from scratch, that would be an awful lot of work. >> That it would indeed.. But at the same time, we would need to go through >> everything and clean out a lot of old/bad examples anyway. I'd say, >> unless we're to keep the old site totally, we need to go through all >> pages and move/filter the content. >> > This, yes. My concern was about authorship and copyright mostly. > "© Copyright 2003-2016 - OWFS website" isn't a good thing to start with. > > > Kind regards > > Jan > > ------------------------------------------------------------------------------ > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers > ------------------------------------------------------------------------------ _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
