Discourse will do all and it's also mobile friendly unlike the old fourm. The problem is that we would need someone to donate server space and power and to run and maintain it. However we would be independent and not tied down by the limitations of Tumbler, deviantart, google, ect just like it was before.
However, an alternative would be to use Google Plus Community groups which are nice as well. I've maintaining one for Jupiter Broadcasting for a couple of years now and it working fine for me.The only downside is that people would need a Google account which may be unsettling for more of the privacy concern people. But as far as "free forums" are concern this would be the best option. On Sun, Nov 15, 2015 at 7:59 AM Andrew Chadwick <[email protected]> wrote: > What would we need from a new forums system if we chose to go that > way? Just a few ideas here: > > - A really important aspect of the forums is to let people share their > artwork, painting tips, and resources (and frustrations, general > comments on the world, inspirations...) > > - A WYSIWYG post editor would be needed, with simple ways of doing > multimedia attachments. We're dealing with regular people here, not > programmers. > > - I'd probably replace any bug report subforums with just a link to > the issue tracker :) The same might be said for suggestions too, or we > could declare the forums as bluesky thinking / possibly-impractical > brainstorming territory and the tracker as the place to bring your > idea when you have mockups and snippets of code etc. (Shorter: don't > make me think it through for you!) > > - We'd need file upload for resource sharing. > > Question is, do more modern approaches like curated Tumblrs (e.g. > http://made-with-mypaint.tumblr.com/) or uses of Github fit some/any > of these requirements? > > - There is already a PR for splitting out the brush collection to a > submodule or a separate project. But it would still be "the brushes > that ship with MyPaint", not a distribution system. > > - Currently the Wiki is open and editable, and is also the place we > link brushes from. But they're only links. > > - We're not going to know about good proposals coming through the > system unless people share them as PRs or new issues. But maybe that's > OK? > > > On 15 November 2015 at 15:42, Andrew Chadwick <[email protected]> > wrote: > > TBH, maintaining forums would be just a headache for me. If we want > > those, I would have to hand over moderation duties basically > > completely because I simply don't have the time for it. > > > > Sorry for being so lax on monitoring the forums. If they come back in > > their existing form, I will have to hand over the reins on them to > > someone else. > > > > The issue tracker is OK for program feature proposals, and great for > > program bug reports (of course). It's greate for making Big Important > > Decisions too. However I feel it'd be an awful place for artist > > community growth. I need more active report triagers already, and > > would need active post moderators too if we start using it as "the > > forums", whatever that might mean. > > > > There will even come a time when we have to crack down on feature > > proposals on the issue tracker, I worry. I'm becoming burnt out by a > > recent flush of (pretty good) suggestions already, so it's clear that > > even the current picture doesn't scale. > > > > > > On 15 November 2015 at 04:54, Albert Westra <[email protected]> > wrote: > >> Jeykll is a good CMS to use and has a good size user base so good > support > >> and good amount of available themes. Hugo is Faster and simpler to use, > and > >> uses Markdown like Jeykll. After thinking about I would go for Jeykll > since > >> speed isn't really necessary and most people would be familiar with > Jeykll. > >> > >> Now what do we do about the forum? We could switch to discorse, but that > >> will still require someone to maintain a server. Or do we just expand > the > >> issue tracker and use the mailing lists more? Discouse dose mainly use > tags > >> just like how the issue tracker uses lables. Me personally I would just > >> expand the issue tracker. > >> > >> > >> On Sat, Nov 14, 2015, 8:34 PM Andrew Chadwick <[email protected]> > >> wrote: > >>> > >>> http://mypaint.org and http://www.mypaint.org should now be up and > >>> running with a tiny placeholder site. No redirects to other domains. > >>> > >>> I've asked our DNS hosting provider, who also host the redirect sites, > >>> to point [www].mypaint.info at mypaint.org. IMO this is a good > >>> redirect to have, since I've been secretly rewriting links to point at > >>> mypaint.org for about a year. > >>> > >>> It may be that we have to just migrate the old content somewhere else, > >>> which could be interesting. > >>> If we do that, perhaps it's worth rebuilding the site properly. > >>> > >>> Any modern CMS or site builder that allows gh-pages hosting would be > >>> great for sharing out the site work. I just happen to like Jekyll > >>> because it's there in my Debian distribution (so lazy). Markdown > >>> appeals to my programmer brain and makes nice diffs. > >>> > >>> _______________________________________________ > >>> Mypaint-discuss mailing list > >>> [email protected] > >>> https://mail.gna.org/listinfo/mypaint-discuss > >> > >> > >> _______________________________________________ > >> Mypaint-discuss mailing list > >> [email protected] > >> https://mail.gna.org/listinfo/mypaint-discuss > >> > > > > > > > > -- > > Andrew Chadwick > > > > -- > Andrew Chadwick > > _______________________________________________ > Mypaint-discuss mailing list > [email protected] > https://mail.gna.org/listinfo/mypaint-discuss >
_______________________________________________ Mypaint-discuss mailing list [email protected] https://mail.gna.org/listinfo/mypaint-discuss
