[Osmf-talk] microgrants - second draft policy document

[Joost Schouppe]

Hackmd because it looks nice and is just generally awesome for editing text
together
Etherpad because it shows off who typed what easily, so nicest to use
during a meeting
LibreOffice because we share an odt file
Word because I was on my work computer and that's what's installed there

So no fundamental choices behind all this, just "whatever works".

I think hackmd could be the tool to use for this though. It is both
extremely easy to use, allows for some layout with markdown, and it shows
edit history. I believe you can create published versions and share a read
only link. I have not looked into exportability of the edit data though.

Whether or not the detailed edit data - should- be shared is another
matter. I think it could be useful, as it would help for our members to
have a closer understanding of how the board works and who stands where.
But it can also be misleading: for example someone might make an edit after
wider discussion, a compromise that does not reflect their personal point
of view at all. Apart from that, I do think there are situations where
there is a trade-off between transparency and efficiency. If I have to
choose, I'd rather have a board that is working for osm than one that is
paralyzed by fear of attack. When it's your work being analyzed, scrutiny
feels a lot like constant attacks. I know that's not what's happening, but
it can be exhausting. And burned out board members aren't good for the
OSMF. Now I know all this can be an easy excuse to just do everything
behind closed doors. I hope you don't r read that into this. Personally, I
hope that in this new board, that seems to have less trust issues, we can
adopt a more open working culture.

Joost



Op di 14 jan. 2020 11:08 schreef Christoph Hormann <chris_hormann at gmx.de>:

> On Tuesday 14 January 2020, Allan Mustard wrote:
> > I don't know of a software product that can parse versions across
> > multiple platforms and software products.  If anybody does, please
> > let us know.  Especially if it is freeware.
>
> As Roland already mentioned git and other version control systems are
> well suitable for this, especially if you work based on text based
> formats (Markdown, Mediawiki, LaTex etc.)
>
> There are editors with direct RCS integration but most people prefer to
> do this separately - checking out the current state of the file, making
> edits and then committing the changes.  If you for some reason need to
> do format conversion because your chosen exchange format is not
> supported by your editor that would need to be done as well of course.
> But unless you are extremely partisan about this ("i only do text
> editing in Word") just pick a suitable editor.  Always keep in mind
> that we are not talking about fancy DTP work here, this is about simple
> text documents - headings, paragraphs, lists, occasionally a small
> table.  Using OpenOffice is already complete overkill for that.  I
> would do things like that in a plain text editor without WYSIWYG
> anyway.
>
> The most strait away method if you are not familiar with version control
> systems is of course just editing the document on the wiki - especially
> if it is, like here, a document that will ultimately reside on the wiki
> anyway.  But i understand this comes with disadvantages (very limited
> editing interface, no comfortable offline editing ability).  But it has
> the advantage that most people in the OSM community are familiar with
> it.
>
> --
> Christoph Hormann
> http://www.imagico.de/
>
> _______________________________________________
> osmf-talk mailing list
> osmf-talk at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/osmf-talk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osmf-talk/attachments/20200114/f1e8b6ff/attachment.htm>