emilioeduardob / mailr

ruby on rails webmail client
MIT License
4 stars 2 forks source link

Mailr reactivation? #9

Closed musashimm closed 13 years ago

musashimm commented 13 years ago

Hi everybody, I let myself to open this issue in Emilio repo to start discussion about mailr project. Everybody interested in project can comment this issue.

I see some key issues we must address before we start development:

  1. Do we have resources (mainly free time) to handle project and reactivate him. Everybody should declare if he can support project. Then we decide what to do.
  2. One place for repository. It can be Emilios repo for much resent development or Luben as a initial author. Whatever wiil be chosen Luben if it possible please do link on mailr.org pointed to github as reliable source (i think that GitHub is a good place for that).
  3. The plan of development:
    • switch to Rails 3 - we have two options:
      • development from scratch - disadvantage timeconsuming - advantage fresh start to maintain project
      • make necessary changes to make it usable based rails 3 and upgrades components step by step.
    • integrate some theme plugin for example themes_for_rails. In my opinion if we want everybody to use mailr, it must have good, modern and customizable "look and feel".
    • Move as much parameter as possible from default_site.rb to Preferences Tab. All or almost all configuration should be done through web interface. It will increase usability.

Please comment above.

emilioeduardob commented 13 years ago

hi! I do have some free time to spend on it, although this last few weeks i practicaly had none. I had a designer work on the UI to make it more profesional looking and the finished theme is on www.mec.gov.py/mailr that address is of the Ministry of Education in Paraguay that is trying to switch to mailr and is testing it. You can try user: emilio , password: emilio to look at the theme. So i can with no problem translate all to spanish.

I have no problem whether is my repo or Luben. It's important to link mailr.org to the freshest github repo.

I'd say we could start fixing the current code instead of starting from scratch. +1 for moving all the parameters.

Emilio

2011/6/22 musashimm < reply@reply.github.com>

Hi everybody, I let myself to open this issue in Emilio repo to start discussion about mailr project. Everybody interested in project can comment this issue.

I see some key issues we must address before we start development:

  1. Do we have resources (mainly free time) to handle project and reactivate him. Everybody should declare if he can support project. Then we decide what to do.
  2. One place for repository. It can be Emilios repo for much resent development or Luben as a initial author. Whatever wiil be chosen Luben if it possible please do link on mailr.org pointed to github as reliable source (i think that GitHub is a good place for that).
  3. The plan of development:
    • switch to Rails 3 - we have two options:
      • development from scratch - disadvantage timeconsuming - advantage fresh start to maintain project
      • make necessary changes to make it usable based rails 3 and upgrades components step by step.
    • integrate some theme plugin for example themes_for_rails. In my opinion if we want everybody to use mailr, it must have good, modern and customizable "look and feel".
    • Move as much parameter as possible from default_site.rb to Preferences Tab. All or almost all configuration should be done through web interface. It will increase usability.

Please comment above.

Reply to this email directly or view it on GitHub: https://github.com/emilioeduardob/mailr/issues/9

lmanolov commented 13 years ago

Hi Wojciech and Emilio,

I am glad that there is still interest in mailr. I will definitely try to find some time for the project. In the beginning I will be rather slow because I have to absorb all the changes in Rails since version 1.2 (when my active Rails development stopped).

I forked Wojciech's repo and changed the license of the project from MIT to Unlicense (unlicense.org). I added both of you as collaborators on https://github.com/lmanolov/mailr and I hope that this means that you should be able to push to the repo. If you are OK to use this repo I will leave the link from mailr.org unchanged, otherwise I will make a link to Emilio's repo.

Best regards,

Luben

emilioeduardob commented 13 years ago

Hi Luben! That's Great! i already saw on my github that i have read/write access to your repo, so I'd say we stick to yours. And don't worry for rails, i don't think there are so many diference with the original version, mostly config files... Thanks! Emilio

2011/6/23 lmanolov < reply@reply.github.com>

Hi Wojciech and Emilio,

I am glad that there is still interest in mailr. I will definitely try to find some time for the project. In the beginning I will be rather slow because I have to absorb all the changes in Rails since version 1.2 (when my active Rails development stopped).

I forked Wojciech's repo and changed the license of the project from MIT to Unlicense (unlicense.org). I added both of you as collaborators on https://github.com/lmanolov/mailr and I hope that this means that you should be able to push to the repo. If you are OK to use this repo I will leave the link from mailr.org unchanged, otherwise I will make a link to Emilio's repo.

Best regards,

Luben

Reply to this email directly or view it on GitHub: https://github.com/emilioeduardob/mailr/issues/9#issuecomment-1426265

musashimm commented 13 years ago

Ok, so Luben repo is as reference. I opened first issue and assigned myself. Emilio could You translate open issues to English. So from now all issues should go to Luben repo: https://github.com/lmanolov/mailr