<p style="margin-bottom:0in">Hello Kdevelop developers,</p><p style="margin-bottom:0in">I have rewritten my proposal a bit. Maybe you can take look at it:</p><p style="margin-bottom:0in"><b>Introduction</b></p>
<p style="margin-bottom:0in">I noticed that deploying applications
to Linux is not that easy, especially when considering that there are
a lot of different Linux distributions out there. OpenSUSE (or
exactly Novell) found a solution for that, the Open Build Service.
The Build Service brings a lot of comfort for developers and
packagers, however to deploy an app with the Build Service, you need
at least do know the basics about RPM and Deb and a lot of time. For
Developers using Linux as main development platform this is of course
not a big problem, but especially when a project is developed for
different platforms, developers might be frightened about deploying
applications to Linux, especially smaller projects. The aim of the
project Bretzn was to connect various services on the internet for
building and deploying applications. In the end of 2010 the beta of a
plug-in for the IDE Qt Creator was released. The plug-in looked very
interesting, but a final version was never released. So my suggestion
is, bringing project Bretzn back to live and to create an application
for deploying software on Linux.</p>
<p style="margin-bottom:0in"><b>The goals of the project</b>:</p>
<ul>
<li><p style="margin-bottom:0in">making deployment of applications
on Linux easy</p>
</li><li><p style="margin-bottom:0in">saving lots of time for releasing
applications and updates on openDesktop.org</p>
</li><li><p style="margin-bottom:0in">providing a plug-in for Kdevelop</p>
</li></ul>
<p style="margin-bottom:0in"><b>Implementation</b>:</p>
<p style="margin-bottom:0in">The project should start where the
development of the Qt Creator plug-in was stopped. The plug-in used
lib Attica, which provides an easy to use framework for using the
Open Collaboration Services. Lib Attica provides support for
connecting to the Build Service as well as the openDesktop platform.
This project will be developed as Kdevelop plug-in, so I will refer
to it as Build Service Plugin. The Build Service Plugin should
automatically generate .spec files for RPM distributions and the
necessary files for Deb distributions. Generating these files might
not be possible for every project without user interaction, but as
the Build Service Plugin is especially targeted to smaller projects,
most of the time containing only a binary, some icons, a desktop file
and some documentation, this should be possible. The GUI should
provide an easy way to input data like the application description or
the change log. After all the necessary file are created, the project
will be uploaded to the Build Service. Another idea is that the Build
Service Plugin also provides an easy way to publish projects to the
openDesktop.org platform, where end users can find, comment and rate
applications.</p>
<p style="margin-bottom:0in"><b>Timeline:</b></p>
<ul>
<li><p style="margin-bottom:0in">Before GsoC:
Analyzing the code of the previous project and getting information
from the developers</p>
</li><li><p style="margin-bottom:0in">Designing the
user interface and how the application should work</p>
</li><li><p style="margin-bottom:0in">Implementing
the specfile and debian.rules generator</p>
</li><li><p style="margin-bottom:0in">Implementing
the project-file management and tarball creator</p>
</li><li><p style="margin-bottom:0in">Implementing
the parts of the application that use the OCS API (the network part)</p>
</li><li><p style="margin-bottom:0in">Creating the
Kdevelop plug-in</p>
</li><li><p style="margin-bottom:0in">Creating the
documentation (most should already be done during development
process)</p>
</li><li><p style="margin-bottom:0in">Sending code
to Google</p>
</li><li><p style="margin-bottom:0in">After GsoC:
Getting in touch with users, optimizing, bug fixing etc...</p>
</li></ul>
<p style="margin-bottom:0in">Especially because a lot of the tasks
that should be done are well documented, all this should be done
within one to two months, providing enough time if problems, or
things that where not thought of, occur.</p>
<p style="margin-bottom:0in"><b>About me:</b></p>
<p style="margin-bottom:0in">I am
studying electronic engineering at the University
of <em><span style="font-style:normal">A</span></em><em><span style="font-style:normal">pplied
Sciences Technikum</span></em> Vienna.
I have a lot of experience developing Qt applications, because I am a
open source developer since a long time. (one of my newest projects
is PhyxCalc:
<a href="http://kde-apps.org/content/show.php/PhyxCalc?content=149161">http://kde-apps.org/content/show.php/PhyxCalc?content=149161</a>)
I am also one of the OpenSUSE ambassadors for Austria, making me
especially suitable for this job as developer of the Build Service
plug-in.</p><p style="margin-bottom:0in">Thank you for reading my proposal.</p><p style="margin-bottom:0in">Regards</p><p style="margin-bottom:0in">Alexander</p><br><div class="gmail_quote">2012/3/21 Alexander Rössler <span dir="ltr"><<a href="mailto:mail.aroessler@gmail.com">mail.aroessler@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><div>>- You say you want to make a standalone application and then you say<br>> you want to make a plugin. We don't want the application's GUI inside<br>
> KDevelop, that's not useful. If you don't want it integrated with the<br>
> IDE then don't, but don't try to say everything to see if something<br>> gets us interested.</div></div><div>Maybe a plug-in is a better solution, considering build and install, but it might not be necessary to put the whole application into KDevelop.</div>
<div>A standalone application might be a more general solution, not only for KDevelop.</div><div class="im"><div><br>> - Forget about getting in touch with the users. There will be no time<br>> for that. You can do that later if you're still interested in your<br>
> project after the summer is over. (note that you're deciding what to<br>> work on here, so please try to do something that you're interested in)</div></div><div>Ok.</div><div class="im"><div><br>> - Designing the parts of the UI and reading the code should happen<br>
> mostly before the code part starts (here you didn't specify, maybe you<br>> should take a look into google's schedule). Furthermore, you should<br>> have specified in the proposal what this piece of code is going to do.<br>
> That's not what the UI design is about, but from the functionality to<br>> the actual design there won't be that much changes. We need to make<br>> sure that you know what you're doing.</div></div>
<div>Is there any place where I can get more information about that?</div><div class="im">
<div><br>> - Do you really expect to generate rpm and debian spec files automatically?</div></div><div>I think it should be possible to generate rpm and debian spec files for standard projects,</div><div>considering that most applications only consist only of a binary, a desktop file, some data and maybe a documentation.</div>
<div>The build shouldn't be a problem, but the install part might a bit more tricky. There are to ways to install the application:</div><div>via a make file generated by a build tool like automake, cmake, qmake, ... or directly copying files with the spec file. </div>
<div>For smaller projects maybe the second method is easier. However, it should be possible to edit the configure, build and install commands </div><div>manually.</div><span class="HOEnZb"><font color="#888888"><div><br>
</div><div>Alexander</div></font></span><div class="HOEnZb"><div class="h5"><div><br><div class="gmail_quote">
2012/3/21 Aleix Pol <span dir="ltr"><<a href="mailto:aleixpol@kde.org" target="_blank">aleixpol@kde.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, Mar 20, 2012 at 9:46 PM, Alexander Rössler<br>
<div><div><<a href="mailto:mail.aroessler@gmail.com" target="_blank">mail.aroessler@gmail.com</a>> wrote:<br>
> Here I'm starting with my proposal:<br>
><br>
> Please read it and help me improving it.<br>
><br>
> Introduction<br>
><br>
> I noticed that deploying applications to Linux is not that easy, especially<br>
> when considering that there are a lot of different Linux distributions out<br>
> there. OpenSUSE (or exactly Novell) found a solution for that, the Open<br>
> Build Service. The Build Service brings a lot of comfort for developers and<br>
> packagers, however to deploy an app with the Build Service, you need at<br>
> least do know the basics about RPM and Deb and a lot of time. For Developers<br>
> using Linux as main development platform this is of course not a big<br>
> problem, but especially when a project is developed for different platforms,<br>
> developers might be frightened about deploying applications to Linux,<br>
> especially smaller projects. The aim of the project Bretzn was to connect<br>
> various services on the internet for building and deploying applications. In<br>
> the end of 2010 the beta of a plug-in for the IDE Qt Creator was released.<br>
> The plug-in looked very interesting, but a final version was never released.<br>
> So my suggestion is, bringing project Bretzn back to live and to create an<br>
> application for deploying software on Linux.<br>
><br>
> The goals of the project:<br>
><br>
> making deployment of applications on Linux easy<br>
><br>
> saving lots of time for releasing applications and updates on<br>
> openDesktop.org<br>
><br>
> providing a plug-in for Kdevelop<br>
><br>
> Implementation:<br>
><br>
> The project should start where the development of the Qt Creator plug-in was<br>
> stopped. The plug-in used the lib Attica, which provides an easy to use<br>
> framework for using the Open Collaboration Services. Instead of developing<br>
> this project purely as Kdevelop plug in, I would prefer developing a<br>
> standalone application and providing a plug-in that makes use of this<br>
> application. The application should automatically generate .spec files for<br>
> RPM distributions and the necessary files for Deb distributions. Data like<br>
> the application description or the changelog could be input with an easy to<br>
> use GUI.<br>
><br>
> Timeline:<br>
><br>
> Analyzing the code of the previous project and getting information from the<br>
> developers<br>
><br>
> Designing first parts of the GUI<br>
><br>
> Implementing the specfile and debian.rules generator<br>
><br>
> Implementing the project-file management and tarball creator<br>
><br>
> Implementing the parts of the application that use the OCS API<br>
><br>
> Finishing the GUI<br>
><br>
> Creating the Kdevelop plug-in<br>
><br>
> Getting in touch with the users<br>
><br>
> Testing<br>
><br>
> Optimizing and bug fixing<br>
><br>
> Especially because a lot of the tasks that should be done are well<br>
> documented, all this should be done within one to two months, providing<br>
> enough time if problems, or things that where not thought of, occur.<br>
><br>
> About me:<br>
><br>
> I am studying electronic engineering at the University of Applied Sciences<br>
> Technikum Vienna. I have a lot of experience developing Qt applications,<br>
> because I am a open source developer since a long time. (one of my newest<br>
> projects is PhyxCalc:<br>
> <a href="http://kde-apps.org/content/show.php/PhyxCalc?content=149161" target="_blank">http://kde-apps.org/content/show.php/PhyxCalc?content=149161</a>) I am also one<br>
> of the OpenSUSE ambassadors for Austria, making me especially suitable for<br>
> this job as developer of the Build Service plug-in.<br>
><br>
><br>
> Regards<br>
> Alexander<br>
><br>
> 2012/3/17 Aleix Pol <<a href="mailto:aleixpol@kde.org" target="_blank">aleixpol@kde.org</a>><br>
>><br>
>> On Fri, Mar 16, 2012 at 9:27 PM, Alexander Rössler<br>
>> <<a href="mailto:mail.aroessler@gmail.com" target="_blank">mail.aroessler@gmail.com</a>> wrote:<br>
>> > Hello kdeveleop-developers,<br>
>> ><br>
>> > I'm an electronic engineering student form Austria and I like to apply<br>
>> > for<br>
>> > kdevelop on GSoC. I am using kdevelop as my preferred development<br>
>> > environment for C and so I would like to help you improving kdevelop at<br>
>> > GSoc. I have a lot of experience with Qt/C++, KDE and Linux and I am<br>
>> > also<br>
>> > OpenSUSE ambassador for Austria. As you can see, I'm not new to the open<br>
>> > source community. If you like to see my current Qt project<br>
>> > visit: <a href="http://kde-apps.org/content/show.php/PhyxCalc?content=149161" target="_blank">http://kde-apps.org/content/show.php/PhyxCalc?content=149161</a><br>
>> ><br>
>> > I like your GSoC ideas for kdevelop, but I have following to add: When I<br>
>> > developed PhyxCalc I came to one point, where I had to deploy my<br>
>> > application<br>
>> > for several Linux desktops. As I am a OpenSUSE user, I knew the Open<br>
>> > Build<br>
>> > Service very well. So I deployed my application via the build service,<br>
>> > however, it was quite a pain to get everything working. New developers,<br>
>> > especially developers coming from Windows, might be deterred of the<br>
>> > deployment of applications on Linux (without the build service it is<br>
>> > even<br>
>> > more a pain). So I found this on the<br>
>> > internet: <a href="http://qt-project.org/forums/viewthread/2890" target="_blank">http://qt-project.org/forums/viewthread/2890</a> This plugin is<br>
>> > not<br>
>> > developed any more (and wasn't finished anyway), but I think it would be<br>
>> > nice if kdevelop would have such a plugin. Especially for small projects<br>
>> > this would be perfect, it would make deploying applications for Linux<br>
>> > easy<br>
>> > (and even improve the success of the open source community).<br>
>> ><br>
>> > Regards<br>
>> > Alexander Rössler (aka Strahlex)<br>
>> ><br>
>> > --<br>
>> > KDevelop-devel mailing list<br>
>> > <a href="mailto:KDevelop-devel@kdevelop.org" target="_blank">KDevelop-devel@kdevelop.org</a><br>
>> > <a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
>> ><br>
>><br>
>> Hi Alexander!<br>
>> Yes it's a good idea and something that can be useful, but it also has<br>
>> to be properly thought through before making a proposal out of it.<br>
>><br>
>> I'll be looking forward to your proposal.<br>
>><br>
>> Aleix<br>
>><br>
>> --<br>
>> KDevelop-devel mailing list<br>
>> <a href="mailto:KDevelop-devel@kdevelop.org" target="_blank">KDevelop-devel@kdevelop.org</a><br>
>> <a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
><br>
><br>
><br>
> --<br>
> KDevelop-devel mailing list<br>
> <a href="mailto:KDevelop-devel@kdevelop.org" target="_blank">KDevelop-devel@kdevelop.org</a><br>
> <a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
><br>
<br>
</div></div>Hi Alexander,<br>
All in all, it's a good proposal, although it still lacks some work.<br>
<br>
- First of all, it's KDevelop, writing a project's name properly is a<br>
good start.<br>
- You say you want to make a standalone application and then you say<br>
you want to make a plugin. We don't want the application's GUI inside<br>
KDevelop, that's not useful. If you don't want it integrated with the<br>
IDE then don't, but don't try to say everything to see if something<br>
gets us interested.<br>
- Forget about getting in touch with the users. There will be no time<br>
for that. You can do that later if you're still interested in your<br>
project after the summer is over. (note that you're deciding what to<br>
work on here, so please try to do something that you're interested in)<br>
- Designing the parts of the UI and reading the code should happen<br>
mostly before the code part starts (here you didn't specify, maybe you<br>
should take a look into google's schedule). Furthermore, you should<br>
have specified in the proposal what this piece of code is going to do.<br>
That's not what the UI design is about, but from the functionality to<br>
the actual design there won't be that much changes. We need to make<br>
sure that you know what you're doing.<br>
- Do you really expect to generate rpm and debian spec files automatically?<br>
<br>
I hope this helps you find a better way to explain yourself.<br>
<div><div><br>
Aleix<br>
<br>
--<br>
KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kdevelop.org" target="_blank">KDevelop-devel@kdevelop.org</a><br>
<a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br>