Georg Brandl napisał(a):
>> Fully agreed. I think that I have to look at every piece of this
>> project from two perspectives: (1) a person who only wants to read
>> the docs and (2) a developer, who wants to browse the comments
>> in most efficient way.
[...]
> That all sounds very nice.
That's great, thanks. So, to sum up current discussion:
- it's not that obvious that we'll utilize Django.
That's fine for me, but I don't think I am able
to make mindful and argumentative choice for other
framework, because the only one I know is Django.
If you have your favourite and you know that it'll
make our lives easier, then tell me and I'll learn it.
There's a whole lot of time, before GSoC starts.
- I agree that it would be a lot simpler for developers
to be able to commit changes right from the web app.
Thus, we have to add support for VCSs (and I think
we could hide it all under the 'developer' switch)
- I think that we shouldn't separate post forms for
comments and post forms for diffs. It only adds confusion.
Docs are docs and they shouldn't have an airplane-like
interface.
Please, take a loot at the post form at
http://book.realworldhaskell.org/
I think that ours should be quite similar,
but there should be a tick like:
"I would like to add a diff". When you click on it,
one more input window appears. This window is filled
with the text from the paragraph. In this window
you can change the text itself (the diff will be generated
automatically), and in the 'comment' input window you can
add your comment (I assume that diffs can be commented as well).
When "I would like to add a diff" tick is true,
then you can't post a comment, but you can post a diff.
When it's false, then you can post a comment.
Now, there should be two forums under each paragraph.
One for comments and one for commits. Users should,
by default, see the one for comments, while developers
should have easier access to the commit proposals.
I think that users should have a way to view the commit
proposals discussions, so they can add their voice,
but usually they rather don't like to be bothered with
the diffs and discussions about it.
So, my view is: one post form, but two forums under each
paragraph + all the things I have said in my previous mail
about treating users and developers in different ways.
- design details are a matter of further discussion.
Georg likes the way it's done in RWH docs and I like it too,
but we'll have to do it a lot nicer ;-)
My point is that it's more portable, than the Django
Book way which is not working on Max's IE8 and mine Opera9.
Any suggestions are welcomed and will be welcomed if I ever
get accepted :)
> The problem is that if a user submits something that is going to be
> committed, he must place it under the license of the project and/or assign
> the copyright for the contribution to the project, even if the contribution
> is trivial.
OK, thanks for explanation, I get it now. I think that we can deal with
it easily.
I will sum up the rest of the discussion later this evening.
Thanks for your feedback, guys,
Wojtek
--
Regards,
Wojtek Walczak,
http://tosh.pl/gminick/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sphinx-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sphinx-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
