Hi Mikalai,

It's good that you had a look on 3.0.0 documents but latest is 4.0.0. 4.0.0
has a lot of architectural improvements and i'm sure you will understand
them quickly. Refer [1] for 4.0.0 docs.

Regarding developer setup,
I think we have few guys who are working on running Stratos on Openstack
(with docker). So if you want to run Stratos within one machine, you can
have some guidance from them.
Otherwise you can get a dedicated machine and setup Openstack.
You can follow guides at[1]  for setting up developer environment.

Thanks

[1] https://cwiki.apache.org/confluence/display/STRATOS/4.0.0-Incubating


On Tue, Mar 18, 2014 at 2:58 PM, Mikalai Parafeniuk <parafen...@yandex.by>wrote:

> Hello!
>
> My name is Mikalai Parafeniuk and I am interested in applying to Apache
> Stratos project during GSOC 2014 program. I am interested in the following
> projects: [1], [2], [3]. I'll decide which of them is the most interesting
> to me in the nearest future.
>
> I have already introduced myself a little bit in [3], but I think I can do
> it again. I am final year CS student from Belarus (UTC+3). I am experienced
> with Java, Python, C++, have 3 years of industrial programming. I have
> successfully participated in Apache project during GSOC 2012. Also I love
> math, algorithms and machine learning. Regarding Stratos project: I am
> interested in cloud computing and applying to Stratos seems a great
> opportunity to learn an internals of enterprise level Paas system.
>
> I learned about GSOC timeline too late, so I applied only 5 days ago. I
> had no response for that days, so now I am just familiar with documentation
> (3.0.0 version). I read architecture section carefully and it seems quite
> clear to me, and also I ensured that I am interested in this project. Also
> I have looked through developer and user guides. So, I think, the next
> logical step will be to write some code! As Lahiru Sandaruwan suggested, I
> looked through minor bugs [4]. It seems that there are a lot of them and
> not all of them are trivial.
>
> So, I got some questions for developers:
> 1) Can I start writing proposal for GSOC right now? I worry, because right
> now I have no contributions to project. Is it ok to put link to my ASF Jira
> account activity in proposal and submit patches afterwards? It will take
> some time to setup development environment, select some issues to work
> among 66 suggested.
> 2) Each of project [1] [2] [3] seems interesting to me. Which advice a
> community can give? Which project is the most interesting/desireable to
> implement?
> 3) I failed to find some kind of "Getting started" tutorial for
> developers. As far as I understood the developers guide [5] is aimed on
> developers who *use* Stratos. Can anyone provide me some information
> about how to setup development environment, which prerequisites exist for
> developers of Stratos, how changes in code are tested etc.
> 4) How process of submitting code works? Can I use fork/pull-request
> scheme with Github or should I submit patches to Jira issues?
> 5) Do I need to setup working instance of Stratos to submit some code?
> Getting started tutorial [6] seems to be quite complicated and has a lot of
> prerequisites.
>
> [1] https://issues.apache.org/jira/browse/STRATOS-488
> [2] https://issues.apache.org/jira/browse/STRATOS-497
> [3] https://issues.apache.org/jira/browse/STRATOS-506
> [4]
> https://issues.apache.org/jira/browse/STRATOS-491?jql=project%20%3D%20STRATOS%20AND%20priority%20%3D%20Minor<https://issues.apache.org/jira/browse/STRATOS-491?jql=project%20=%20STRATOS%20AND%20priority%20=%20Minor>
> [5]
> https://cwiki.apache.org/confluence/display/STRATOS/3.0.0+Developer+Guide
> [6]
> https://cwiki.apache.org/confluence/display/STRATOS/3.0.0+Getting+Started
>



-- 
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

email: lahi...@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146

Reply via email to