No description provided.
renamed to markdown
Various updates prior to posting for community review.
incorporated suggestions from mailing list/dw posts
Added terms of service
Merge pull request #1 from Skud/master
Terms of service
Updated TOS with version for soft launch
tiny tweaks to community guidelines
Added copyright infringement policy
added API and Data Use Policy
Added section numbers and changes section
Added links to CC licenses
This is mostly just for display on github.
tweaked intro paragraphs
added 'tried to make this readable'
added 'tried to make this readable' to api policy
Merge pull request #3 from Skud/softlaunch
policy for soft launch
Adding config for email addresses and using it in policies
Correcting config variables to use right class
Undoing notifier change as it's not working yet
Get notification email "from" address from app config.
this should just be email@example.com -- no point in separating it out to be staging particularly.
Our thought here was to reduce confusion for people testing multiple deployments of the app.
Again, just make it firstname.lastname@example.org ... I don't see what point there is in separating this out.
This is risky. Our policies are actually kept in the Growstuff/policy repo, which is their official home. If/when we update them, we copy the content of each policy across to Growstuff/growstuff. This gives us a couple of advantages:
The downside is that with the copy-pasting across, any code in the views (such as the call to the config, here) will be overwritten. But if we include it in the policy repo, it will be unreadable by the humans who might go there to take a look.
Not sure what the end result of this should be. It's confusing.
Not sure what the correct solution is to the email address issue (if someone forks the site then we don't want to get media queries relating to their deployment!), but it might make more sense to use git-submodule or git-subtree to handle the inclusion rather than explicitly copying-and-pasting documents. I have used git-submodule and found it fairly straightforward, but I'm told git-subtree (which I haven't used) is better.
Removing policy folder in preparation for lining it up with policy re…
Add 'app/views/policy/' from commit '55eda9ef694388e61464fa406033c079…
Removed unnecesarry readme and renamed policy files
for Growstuff code repository version of policy
using git subtree
Wrap policy in haml and make email addresses configurable
Merge pull request #2 from cesy/emailconfig
Make site_name, company_name and host_name config vars.
Include policy .mds from HAML
git-subtree doesn't like us for having renamed files. This was our
attempt to fix that. It doesn't work :-( None of the embedded code in
the Markdown files gets interpreted.
This seems to be stalled/insoluble for now. Closing; we can reopen sometime later if we figure out what we want to do.