Features and Priorities

[Mária Jurčovičová <m....@gmail.com>]

Hi,

I'm new to this project and I'm looking for something to do. I went through
all open unassigned issues in Jira. It seems to me, that Shiro is almost
done. Is that so, or are there some missing wanted features?

Another question is: which issues are more important than others? I would
like to do something, but I do not want to fix issues nobody cares about.

With Regards,
Maria Jurcovicova

Re: Features and Priorities

[Phil Steitz <ph...@gmail.com>]

On 6/11/11 2:20 PM, Les Hazlewood wrote:
> Hi Maria,
>
> Thanks for offering to help out!  We can only be a better project when
> people like yourself offer to help.
>
> In addition to what Kalle has said, I just created a new search filter
> in Jira for our project.
>
> https://issues.apache.org/jira/browse/SHIRO
>
> On the top navigation bar, click the 'Issues' drop-down arrow (not the
> actual 'Issues' word).  You should see at the bottom of that drop-down
> a filter named: "Most Popular Outstanding Development Issues".  (here
> is the direct link:
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12315660)
>
> This is just my opinion, but this is probably the best indicator of
> what to work on next, as it orders things based on how much the
> community wants something. Of course, this is open source so you have
> the luxury of working on whatever you want if it interests you, but
> this filter is what I use to see what I should work on next, so I
> thought I'd point it out.
>
> Also, note that while an issue may be assigned to one of the team
> members already, that doesn't mean you can't/shouldn't work on
> something - if you see the issue hasn't been updated in a while, odds
> are high that the person to whom it is assigned probably hasn't
> touched it in a while and you could probably help out if you wanted.
> If you're interested in working on an already-assigned issue, I'd just
> post a comment on any of those issues to see what the current state of
> them are.

Thanks, Les!

I have also been lurking for a while and thinking about stuff to
work on.  One thing I would add for Maria and anyone else getting
involved @apache is that working on test cases, javadoc and other
documentation is always a great way to get started contributing.

Phil
> HTH!
>
> Best,
>

Re: Features and Priorities

[Les Hazlewood <lh...@apache.org>]

Hi Maria,

Thanks for offering to help out!  We can only be a better project when
people like yourself offer to help.

In addition to what Kalle has said, I just created a new search filter
in Jira for our project.

https://issues.apache.org/jira/browse/SHIRO

On the top navigation bar, click the 'Issues' drop-down arrow (not the
actual 'Issues' word).  You should see at the bottom of that drop-down
a filter named: "Most Popular Outstanding Development Issues".  (here
is the direct link:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12315660)

This is just my opinion, but this is probably the best indicator of
what to work on next, as it orders things based on how much the
community wants something. Of course, this is open source so you have
the luxury of working on whatever you want if it interests you, but
this filter is what I use to see what I should work on next, so I
thought I'd point it out.

Also, note that while an issue may be assigned to one of the team
members already, that doesn't mean you can't/shouldn't work on
something - if you see the issue hasn't been updated in a while, odds
are high that the person to whom it is assigned probably hasn't
touched it in a while and you could probably help out if you wanted.
If you're interested in working on an already-assigned issue, I'd just
post a comment on any of those issues to see what the current state of
them are.

HTH!

Best,

-- 
Les Hazlewood
CTO, Katasoft | http://www.katasoft.com | 888.391.5282
twitter: http://twitter.com/lhazlewood
katasoft blog: http://www.katasoft.com/blogs/lhazlewood
personal blog: http://leshazlewood.com

Re: Features and Priorities

[Kalle Korhonen <ka...@gmail.com>]

2011/6/8 Mária Jurčovičová <m....@gmail.com>:
> I'm new to this project and I'm looking for something to do. I went through
> all open unassigned issues in Jira. It seems to me, that Shiro is almost
> done. Is that so, or are there some missing wanted features?

Hi Maria,

oh no, Shiro is far from done. No code is really ever done. There are
lot of ideas for future development that don't necessarily show up in
Jira just yet (see
https://cwiki.apache.org/confluence/display/SHIRO/Version+2+Brainstorming
for example).

> Another question is: which issues are more important than others? I would
> like to do something, but I do not want to fix issues nobody cares about.

You get a rough idea of the issue's importance from it's priority and
votes. But in general, we care about all issues so if I was you, I
really wouldn't worry about it too much. Work on which ever issue is
interesting to you. We absolutely will go through all the issues at
some point, it's just that the issues that are not important enough
for anybody will take longer to resolve, usually until they become
important enough for somebody to provide a solution for them. The
truly unimportant issues would eventually just be closed out (with end
state set to something like won't fix, works for me).

Kalle