On Thu, Apr 6, 2017 11:19 AM, Florent Daigniere nextg...@freenetproject.org
wrote:
On Thu, 2017-04-06 at 15:08 +, Ian wrote:
> Well, it's an improvement over what we have now even if it is
> incomplete :)
> Just for clarity, what is the procedure for deploying improvements?
Pushing
On Thu, 2017-04-06 at 15:08 +, Ian wrote:
> Well, it's an improvement over what we have now even if it is
> incomplete :)
> Just for clarity, what is the procedure for deploying improvements?
Pushing them to the existing repository on a different branch. Travis
will auto-build/deploy from
Well, it's an improvement over what we have now even if it is incomplete :)
Just for clarity, what is the procedure for deploying improvements?
Now that it's live hopefully multiple people can fork it and start pushing
improvements which we can review and merge.
We should have an approval process
The jnlp download for Linux requires review and almost certainly
modification. I'm not familiar with jnlp itself but I will try to review it
and the rest of the downloads in the next half hour on public transit. I
don't know if I'll have enough time to complete that this morning however,
it would
https://github.com/Ademan-laptop/freenet-website-redesign-pelican/commit/ae6b9c4e2d5f282a120abcfdd4a6c4216586f7e9
This addresses the snags in a kludgy way, but is far super to broken links
since we're live now.
Thanks,
Dan
On Apr 6, 2017 10:36 AM, "Ian Clarke" wrote:
On Thu, 2017-04-06 at 17:19 +, Ian Clarke wrote:
> On Thu, Apr 6, 2017 11:19 AM, Florent Daigniere nextgens@freenetproje
> ct.org wrote:
> > On Thu, 2017-04-06 at 15:08 +, Ian wrote:
> > > Well, it's an improvement over what we have now even if it is
> > > incomplete :)
> > > Just for
I have put a rewrite rule on the bucket; this shouldn't be necessary any
more
Florent
On Thu, 2017-04-06 at 10:52 -0700, Dan Roberts wrote:
> https://github.com/Ademan-laptop/freenet-website-redesign-pelican/comm
> it/ae6b9c4e2d5f282a120abcfdd4a6c4216586f7e9
>
> This addresses the snags in a
I have made the DNS changes; these aren't the problem...
The problem is that the content we serve from the new infrastructure
isn't ready... almost a year in the making... so we have never finished
the infrastructure switch.
Whatever is pushed to
I've created a doc to give quick instructions on how to contribute to the site
and also a list of snags that need to be fixed. Hopefully this can grow into a
quick overview of how everything is wired together here (if Florent or someone
could flesh this out).
Anyone is welcome to address any