mailing-list for TeXmacs Users

[Giovanni Piredda <address@hidden>]

On 11.11.20 13:56, Giovanni Piredda wrote:
> If a curated blog is the one developers see most fit, then I am going 
> to support it even if my initial preference was for a wiki mostly 
> controlled by the users.
>
> Still I think that support for exchange of packages and style files 
> among users would be good (strong benefits could come from this). The 
> blog can do it by publishing articles where users describe their own 
> extensions, with a link to a repository, and organizing these articles 
> into collections.
And advertising that it does it in a prominent place :-)




> G.
>
>
> Am 11.11.2020 um 09:38 schrieb Massimiliano Gubinelli:
> > Dear all,
> >
> >   I've added some guidelines for proposing content for the blog 
> > (https://texmacs.github.io/notes/index.html).
> >
> > You can find them 
> > here:https://texmacs.github.io/notes/editorial-guidelines.html
> >
> > I tend to think that the correct contribution system is a "curated" 
> > one for many reasons:
> >
> > 1) technical: the addition have to be post-processes by knowledgeable 
> > people to ensure that the HTML translation is acceptable and nice.
> >
> > 2) editorial: we want this place to be useful and meaningful. To me 
> > the right approach is to consider it a "publication" where there is 
> > somebody (an editor board) which cares about homogeneity and quality. 
> > So a bit of centralization. This agrees with the fact that TeXmacs 
> > itself (i.e. Joris :)) is very opinionated on design choices and aim.
> >
> > 3) decentralization: the fact that is a git repository means that it 
> > still remains de-centralized to a large extent: if you want you can 
> > clone the repository and publish the material in **any way** you 
> > like. Like software this material will be open source, for all to use 
> > as they see fit.
> >
> >
> > I feel that the editorial policy do not restrict your freedom as 
> > content contributor: if you have a github account is very easy to 
> > publish your own better version as "github pages".
> >
> > Anyway I'm open to discuss it, my intention is that it is 
> > useful/informative/correct/pleasant to read, this should be the 
> > primary goal.
> >
> > Max