If we refactor this properly to be UI independent it will open the door to things like<br>using Debian&#39;s APT for updates! That would be awesome.<br><br><div class="gmail_quote">On Mon, Mar 2, 2009 at 11:16 AM, Nabil Alsharif <span dir="ltr">&lt;<a href="mailto:nabil@gobrighttree.com">nabil@gobrighttree.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Great. This is going to be my first contribution to drupal and I don&#39;t<br>
know what the process for submitting such changes is. Do I open an issue<br>
and attach patches? Or do I have to sign up for a cvs account and commit<br>
via cvs?<br>
</blockquote><div><br>For core, it is always via patches and issues.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Would it be better to submit (patches or commit) partial but working<br>
changes, or should I wait until it&#39;s all done and then submit one big<br>
change?<br>
<div><div></div><div class="Wj3C7c"></div></div></blockquote><div><br>Depends on if you want to get feedback early or feel you have a solid <br>approach that is working.<br><br>I would say since this is your first attempt at core contributions, submit<br>
partial stuff to get feedback. The process can be slow and may dishearten<br>the newbies at first. But if you persist, things will get done.<br></div></div>-- <br>Khalid M. Baheyeldin<br><a href="http://2bits.com">2bits.com</a>, Inc.<br>
<a href="http://2bits.com">http://2bits.com</a><br>Drupal optimization, development, customization and consulting.<br>Simplicity is prerequisite for reliability. --  Edsger W.Dijkstra<br>Simplicity is the ultimate sophistication. --   Leonardo da Vinci<br>