On Wed, Mar 25, 2015 at 3:20 AM, Christopher Sean Morrison <brl...@mac.com> wrote: > > > On Mar 24, 2015, at 4:43 PM, Hitesh Sofat <sofathit...@gmail.com> wrote: > > > Alright we will eliminate MySQL to the extent possible. But in many > > places MySQL is needed to store the information. Example:- sending > > notification to admin about update doc and so on. > > Even this can be handled with a directory queue strategy. It just needs a > ledger of what has and has not been e-mailed yet. This could be handled with > a separate queue or could be a metadata/semaphore file.
Alright. I have not done this before but this seems interesting. I will be glad if you assist / suggest a bit more on this (wanting to try it locally). > If it’s going to require MySQL then it really should probably rely on > existing infrastructure (like being a Mediawiki or Confluence plugin) as that > introduces a whole notion of account management. I wouldn’t want a separate > account management system just to edit docs online… I am thinking of using either mediawiki or wordpress. So the account management system will be used of these CMSs. I would like to be suggested here since I am confused with which I should proceed MediaWiki or Wordpress? I guess this should depend on the direction in which existing infrastructure is moving. > Later on, we’ll need to consider how to let commits be associated with the > right developer. Something like this > http://stackoverflow.com/questions/3304787/commit-to-subversion-on-behalf-of-someone > or migrate just the docs to git and use the --author flag. You’ll have to > test how well that works with services like Ohloh, though, to make sure > changes are credited correctly. Alright. I will explore these. -- Hitesh Sofat hiteshkumarsofat.wordpress.com (Life is a game & winner is not defined, Think about present because future is not defined, unexpected things make the game interesting, if everything goes right then game is boring ) ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel