[okfn-help] [OKFN-LOCAL-coord] How to host public OKFN documents and templates?

[Lucy Chambers]

Lieven.

On Tue, Mar 6, 2012 at 4:41 PM, Lieven Janssen <lieven.janssen at okfn.org>wrote:

> Lucy,
>
> good tip!
>
> On windows I use TortoiseGit: http://code.google.com/p/tortoisegit/
>
> btw isn't it all about the love ;-) let us just all love the things we use
> ourselves but not hate the things that are used by others. Makes life a lot
> easier!
>

I approve :) Will use that in future!

L


>
>
> Lieven
>
>
>>
>> 2012/3/6 Lucy Chambers <lucy.chambers at okfn.org>
>>
>>> At the risk of fanning the mac-hate flames. For mac users, there is
>>> this: http://mac.github.com/ - which has been making my life a lot
>>> easier, it's a simple commit and sync button :)
>>>
>>> Maybe there is something similar for other operating systems...
>>>
>>> Lucy
>>>
>>> On Tue, Mar 6, 2012 at 3:06 PM, Kat Braybrooke <kat.braybrooke at okfn.org>
>>> wrote:
>>> > Hmm. I'm agreed that the only problem with uploading OKFN document
>>> templates
>>> > via Git is that it's hard for most [non-techie] folks to use. However,
>>> > perhaps we don't need everyone to be editing the documents - they just
>>> need
>>> > to be in a place that Local Chapter and other community folks can
>>> easily
>>> > access.
>>> >
>>> > I suggest:
>>> >
>>> > - We make a new Bitbucket Git folder here [1] called something like
>>> > 'Document Templates'
>>> > - We then provide a link to each on the OKFN Wiki under the 'Resources'
>>> > folder [2]
>>> >
>>> > Am forwarding this also to the 'OKFN-help' discussion list in case
>>> anyone
>>> > else has thoughts about how it would be best to publicly host OKFN
>>> documents
>>> > in the future.
>>> >
>>> > Kat
>>> >
>>> > [1] https://bitbucket.org/okfn/assets.okfn.org/src/0fc75035631b
>>> > [2] http://wiki.okfn.org/Handbook#Resources
>>> >
>>> > | Kat Braybrooke | Community Coordinator
>>> > | Global Chapters and OKFestival
>>> > | Open Knowledge Foundation | London
>>> > | OKFN.org | Twitter @kat_braybrooke
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Tue, Mar 6, 2012 at 2:56 PM, Everton Zanella Alvarenga
>>> > <everton.alvarenga at okfn.org> wrote:
>>> >>
>>> >> It's a possibility, Lieven.  But on commons you also have a
>>> >> versioning. It's possible to upload new versions and it keeps track of
>>> >> all the versions on its log page.
>>> >>
>>> >> I would use both solutions, but does everybody would feel confortable
>>> >> in using a git versioning?
>>> >>
>>> >> Tom
>>> >>
>>> >> 2012/3/6 Lieven Janssen <lieven.janssen at okfn.org>:
>>> >> > For versioning purposes I would also put them on the okfn github
>>> repo.
>>> >> >
>>> >> > On the wiki you could provide links to the raw files on the github
>>> repo.
>>> >>
>>> >>
>>> >> --
>>> >> Everton Zanella Alvarenga (also Tom)
>>> >> Open Knowledge Foundation Brasil
>>> >>
>>> >> _______________________________________________
>>> >> OKFN-LOCAL-coord mailing list
>>> >> OKFN-LOCAL-coord at lists.okfn.org
>>> >> http://lists.okfn.org/mailman/listinfo/okfn-local-coord
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > okfn-help mailing list
>>> > okfn-help at lists.okfn.org
>>> > http://lists.okfn.org/mailman/listinfo/okfn-help
>>> >
>>>
>>>
>>>
>>> --
>>> Lucy Chambers
>>> Community Coordinator,
>>> OpenSpending & Data Journalism
>>> Open Knowledge Foundation
>>> Skype: lucyfediachambers
>>> Twitter: @lucyfedia
>>>
>>> _______________________________________________
>>> OKFN-LOCAL-coord mailing list
>>> OKFN-LOCAL-coord at lists.okfn.org
>>> http://lists.okfn.org/mailman/listinfo/okfn-local-coord
>>>
>>
>>
>


-- 
Lucy Chambers
Community Coordinator,
OpenSpending <http://openspending.org/> & Data
Journalism<http://lists.okfn.org/mailman/listinfo/data-driven-journalism>
Open Knowledge Foundation <http://okfn.org/>
Skype: lucyfediachambers
Twitter: @lucyfedia <https://twitter.com/#!/lucyfedia>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/okfn-help/attachments/20120307/b9cb1701/attachment.html>