On 04/05/2016 11:16, Tushar Mishra wrote:
On Wed, May 4, 2016 at 1:06 PM Francesco Chicchiriccò <[email protected]>
wrote:
On 03/05/2016 23:49, Tushar Mishra wrote:
Sure, I am already reading up on open issues so I can start working on some
small ones right away.
Fine, please report which ones have attracted your attention, I'll be
happy to assign them to you and to review you PR(s).
One issue that I myself faced was SYNCOPE-839
<https://issues.apache.org/jira/browse/SYNCOPE-839>. I looked into it and
ran an update on all the snapshots on remote repositories using -U and
found this problem.
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache Syncope sample project - Console 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading:
http://repo.maven.apache.org/maven2/org/apache/syncope/fit/syncope-fit-build-tools/2.0.0-M2/syncope-fit-build-tools-2.0.0-M2.pom
[WARNING] The POM for
org.apache.syncope.fit:syncope-fit-build-tools:war:2.0.0-M2 is
missing, no dependency information available
Downloading:
http://repo.maven.apache.org/maven2/org/apache/syncope/fit/syncope-fit-build-tools/2.0.0-M2/syncope-fit-build-tools-2.0.0-M2.war
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Syncope sample project ..................... SUCCESS [6.191s]
[INFO] Apache Syncope sample project - Common ............ SUCCESS [1.304s]
[INFO] Apache Syncope sample project - Core .............. SUCCESS [4.938s]
[INFO] Apache Syncope sample project - Console ........... FAILURE [2.515s]
[INFO] Apache Syncope sample project - Enduser ........... SKIPPED
[INFO] ------------------------------------------------------------------------
Turns out the profile of embedded is looking for syncope-fit-build-tools at
http://repo.maven.apache.org/maven2/org/apache/syncope/fit/ which is not
accessible.
If I am heading in the right direction, could you point me someplace where
I could read more about this or figure out a way to solve this?
I have commented SYNCOPE-839 with some details.
One - not particularly fancy, I know - idea could be to help writing and
/ or reviewing our documentation for 2.0.0
https://issues.apache.org/jira/browse/SYNCOPE-700
I'll be reading up on adding documentation for solving SYNCOPE-700
<https://issues.apache.org/jira/browse/SYNCOPE-700> and get back to you
when I have some more information.
You can start by taking a look at Reference Guide's TOC and filling one
of the (multiple) blank chapters and paragraphs there.
I might be able to start again working on this next week.
Regarding the cloud deployment, I was talking about using the Google
Cloud
platform to get a development environment where I can securely deploy
syncope and work on the project. Will it be feasible and what would you
suggest?
Unfortunately I don't have any experience with Google Cloud (maybe
someone else here); possibly you can empower the deb packages
http://syncope.apache.org/docs/getting-started.html#debian-packages
for installing over a Debian / Ubuntu machine, or even take a ride on
Docker with help of our fellow committer Andrea Patricelli:
https://github.com/andrea-patricelli/syncope-docker
I've posted a query
<https://groups.google.com/forum/#!topic/google-summer-of-code-students-list/hxEKAy9stTE>
regarding the usage of a cloud development platform on the GSoC mailing
list (since the tax form states that I cannot use machines based in the US
for the development of the project). I will update you with any progress on
this as well. Until then, I will be using my local machine just to be safe.
Fine.
Regards.
On Tue, May 3, 2016 at 5:14 PM Francesco Chicchiriccò <[email protected]>
wrote:
On 03/05/2016 06:01, Tushar Mishra wrote:
Hello devs,
I would like to update you on my progress regarding the project. I've
downloaded the sources and built them successfully.
That's good.
I've also started
working on the plugin layout which took a bit of a look around to find
the right way to do it.
This is premature: until May 22nd you are in the community bonding
period, e.g. you are not expected to work on your project but instead to
get acquainted with Apache Syncope and its community (see my mail
below).
I would like to ask something at this point. I am able to create a
"view"
in eclipse which shall display in a window, the email templates
available
and clicking on a template would open it in the editor. Now, which of
the
following should I focus on?
- A button in the menu which opens the view in the workbench
- A perspective which displays just the template list view and an
editor
Also, I would like to know if I can use a cloud platform to develop
this
project. It would be easier for me since I work behind a proxy in my
college and also, it would save me the hassle of manually backing up my
work everyday.
Do you want to deploy Apache Syncope in a cloud space of yours (which
one, in case?) or are you looking for a place where it is already
deployed and running? For the latter case you might want to empower
http://syncope.apache.org/demo.html
Regards.
On Fri, Apr 29, 2016 at 2:57 PM Francesco Chicchiriccò <
[email protected]> wrote:
On 27/04/2016 17:39, Tushar Mishra wrote:
Hello devs,
My name is Tushar Mishra and I am currently pursuing a Bachelor’s
degree in Computer Science with specialization in Open Source Software and
Open
Standards from the University of Petroleum and Energy
Studies,Dehradun,India as a 3rd year Undergraduate student.
Recently, my proposal for developing an Eclipse Plugin (as stated in
[SYNCOPE-809]) was accepted at the Google Summer of Code.
Consequently, I have been assigned to the issue under the
supervision of Mr. Francesco
Chicchiriccò who is my mentor for the same.
I look forward to working under your guidance and I believe I can do
wonders with your help.
Hi Tushar,
as your mentor for this activity, let me express my own deep welcome
to
the Apache Syncope community.
Please consider that you are currently in the "Community Bonding
Period"
(Apr 22 - May 22), where you are expected to get ready to start
contributing full time.
Community Bonding activities may involve:
* Becoming familiar with the community practices and processes.
(This often involves a mix of observation and participation.)
* Participating on Mailing Lists / IRC / etc. (Not just
lurking.)
* Setting up their development environment.
* Small (or large) patches/bug fixes. (These do not need to be
directly related to their GSoC project.)
* Participating in code reviews for others. (Even someone who
isn't familiar with the project can contribute by pointing out potential
inefficiencies, bad error handling, etc.)
* Working with their mentor and other org members on refining
their project plan. This might include finalizing deadlines and milestones,
adding more detail, figuring out potential issues, etc.
* If you are already familiar with the organization, you could
be
helping others get involved in the community.
* Reading (and updating!) documentation they will need to
understand to complete their project.
* Reporting or replicating bugs.
In general, I would prefer to keep the communication here, open for
the
whole community. You are naturally free to contact me privately as
you've been doing so far.
Should you need live interaction, let's meet on the #apache-syncope
IRC
channel - I am generally available there from 9.00 AM CET until 6.00
PM CET
Regards.
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC,
Olingo PMC, CXF Committer, OpenJPA Committer
http://home.apache.org/~ilgrosso/
