1.
On Wed, Jun 6, 2012 at 11:13 AM, Steve Ridout <[email protected]> wrote:
We want to focus now on making the style editor the best it can be for
> individual users to edit their styles. It's not in the project scope to
> host user created styles online, or provide an easy method for contributing
> to the styles repo (although they are great ideas).
I'm not going to comment on the specifics (I'll leave that to the client
implementers), but just want everyone here to keep in mind the use cases,
in part so that perhaps some kind of smart coordination can happen to fill
in the gaps on the scope question. Since the code is MIT licensed (and on
github?), there's no impediment for others contributing to this.
So regardless of which of these paths you all want to take for client
integration on the single user case, my question is how we do this in such
a way that the step to social and multi-user is not too large.
Just to repeat and condense my earlier arguments:
1. People don't want to create or edit styles. They just want them to
work.
2. They want to edit style because either there's a bug, or because the
original style author didn't consider a particular kind of source. But
these edit needs typically are not needs specific to the user.
3. They create new styles when they can't find the style they need.
Typical case: they need a style for "Journal X" and can't find it. But
more-often-than-not, "Journal Y" will fill the need. [this is why your work
on the search interface is important Steve]. Again, the needs aren't
specific to the user.
So when we say "we want ... individual users to [be able to] edit their
styles", what do we really mean?
1. What is "their styles"? Is it simply the community created styles
they have access to?
2. Pull out from the single user and consider the hundreds of thousands
of CSL users. How do we make the work for the former contribute to making
life easy for the latter; so they don't feel the need to "edit their
styles" to begin with?
Per Rintze's earlier comments, I think it ought to be possible. Maybe upon
editing a style, for example, there's a "submit to public repository" link
that has a small description field, and which creates a patch and pull
request on the giithub repository?
There would still need to be an easier way to preview changes though for
the repo style editors. And wed need to grow the number of editors.
Bruce
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
