bug-myserver
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-myserver] Google Summer of Code '09 - GUI


From: Giuseppe Scrivano
Subject: Re: [bug-myserver] Google Summer of Code '09 - GUI
Date: Sat, 21 Mar 2009 23:10:45 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.91 (gnu/linux)

"Karol \"Zal\" Zalewski" <address@hidden> writes:

> Hi,
>
>   I have thought about this project and I would like to ask you some
> more questions ;]

I'll try to answer as clearer as I can.

>   - user friendly (maybe two modes - for beginners and advanced users?
> or simple wizard?),

I would avoid to have two separate modes.  It should be easy enough for
beginners and at the same time allow advanced users to do their job.

>   - it must work with configuration written in XML (only with it? what
> about "control protocol"?),

Yes, it must work with configuration written in XML, but better add an
abstraction level here, keeping all the XML related code in a
class/package.  This will add the possibility later to use something
different than XML.
The control protocol offers few commands, the only one you need to
really investigate is file transfer.  If a remote server want to be
managed, then {myserver, virtualhosts, MIMEtypes}.xml are transferred
locally, modified by the user and send back to the remote server.
Shortly, any configuration session is based on these three files, it
should be possible to choose exactly their path.

>   - support for many languages,

do you mean localization?

>   - file manager (like Ivailo wrote),

It has a meaning used together with the control protocol or use the
.security.xml file and allow to change the configuration there.  But
this will be kept for later, if some time will remain at the end of the
summer.

>   - remote configuration.

As said, throught the control protocol.

>   Hmm... maybe it would be better to make web interface (security would
> be a potential problem)? I think it will not be possible to make
> **good** application (tested, without minor bugs) with all above
> functionality in 12-13 weeks. Maybe I am wrong? Could we discuss that on
> mailing list or is it "participants private problem"? :D

This is a subject that can be discussed on a public mailing list without
problems :)

How we will develop the UI is the first decision to take.  Surely a web
interface has many  benefits, first of all that there is need only of a
browser to manage MyServer.  But in the case of a web interface, which
language to use that can be portable on Windows too?

PHP|PYTHON -> you will have to install php|python before you can manage
              the server.
C/C++ -> for a web interface, it is like shooting at yourself.
any other?

Another disadvantage with a web interface is that it requires a
HTTP/HTTPS virtual host while in reality MyServer could be used only
with FTP or any other protocol that can be implemented in future.

>   Could you tell me something more about control protocol? Is it
> described in docs?

There are not documents about the control protocol.  It is not a problem
(from your side) as you will use it trought the py_control_client
library present on the SVN repository.  I don't remember if
py_control_client is missing the file transfer, in that case I will
complete it so you can use it by the GUI. 

>   Actually, to be clear, I want to write something more about me and
> Polish studies. I am not only studying computer science (4th year), but
> also management (2nd year) - both of them daily and on Gdansk University
> of Technology. Yes, studying takes me about 45h for a week, but do not
> worry - I will take dean vacation on management for one semester (CS
> takes me only 14h for a week), when it will be needed.

You are free to manage your time as you want.

>   In Poland we have vacation time in July, August and September. GSoC
> starts (coding) in May 24 and ends in August 24, so I will have only
> about 8 weeks for full time developing and 5 weeks to do it "part time"
> mode. Will it be OK?

As I said you already, the only problem is that GSOC finishes at August
so you will not be able to use your September time for the GSOC, but you
can use this time to complete something missing or bug fixing (you will
not desappear after GSOC, right? :)).

>   Weekly reports, code on Assembla (Mercurial or Git) and live
> communication by IRC/Jabber will be OK for that project. What do you
> think about this?

The development done for GSOC should follow normal rules, it is better
for us to follow you and it is better for you to be part of the
development team.  Any design decision should be take here on the
mailing list so other people can partecipate actively. 
Live communication on IRC/Jabber can be done too keeping in mind that if
important decisions are took there, the discussion must be moved here.
Commits will be done directly to a branch on the MyServer SVN
repository.

Regards,
Giuseppe




reply via email to

[Prev in Thread] Current Thread [Next in Thread]