Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[phoenix-epic-dev] Re: Current Votes for EPIC Themes andPriorities

Ian,
 
Can you be more specific about which of the recommendations your are not comfortable with.  Both recommendation should be very transparent and obvious to anyone casting the vote.  In the 1st recommendation, I neglected to clarify that instead of removing the "bounced" votes email, we actually change its status as "Unconfirmed" but don't count in the overall value.  That is as transparent as it gets.  The only remaining question is if the required effort would justify accommodating anonymous visitors.  We can make that decision at a later point in time.
 
The second recommendation will not prevent people from giving a low vote.  Anyone can do that at any time.  It simply discourages people from just sitting at their computer and giving multiple plugins a low vote (1-3) at the same time.  People only do that for malicious reasons.   The recommendation will stop the same person from giving such low vote in 24 hr increments.  They will be given a message asking them to try again in 24 hrs.  So we will not stop that type of abuse, but make it less convenient for people to do so.  Hopefully the other measures combined will gradually give us a better picture.
 
Maher
 
 
----- Original Message -----
Sent: Wednesday, September 13, 2006 9:45 AM
Subject: Re: Current Votes for EPIC Themes andPriorities

 

I am not comfortable with this approach.  It seems we are creating a level of complexity to accommodate anonymous users.    I think we need to keep things simple and transparent.  This feels too much like we just don’t want negative opinions to be express or alternative it might create the perception we don’t want negative opinions.

 

Ian

 

 


From: phoenix-epic-dev-bounces@xxxxxxxxxxx [mailto:phoenix-epic-dev-bounces@xxxxxxxxxxx] On Behalf Of Maher Masri
Sent: September 12, 2006 1:58 PM
To: The EPIC component of Phoenix
Subject: [phoenix-epic-dev] Re: Current Votes for EPIC Themes and Priorities

 

I spoke to Eric Clayberg regarding his recommendations and would like to provide the following proposal;

 

1-  Keep items 1,2 & 4 from proposed action items as discussed on the call.  Defer item #3 for a follow-on set of initiatives.  Eric and I collaborated on an elegant solution for item 3 that would require more effort than we are currently prepared to tackle in the 1st pass, but will button-up the concerns discussed on the call.  The high-level logic include:

       

        - Require anonymous users to provide an email address when voting at EPIC

        - Validate email address through regular _expression_ logic and ping the mail server to determine its valid.  This step will insure a properly formatted email address form a legitimate email server, but will not validate that the address is real.

        - At the conclusion of the voting process, send a thank you email to the provided address and post the vote results

        - Process bounced emails and remove any vote matching such email with a "Hard" bounce status.  Instantiations might be able to contribute bounce back handling logic so we don't have to write one from scratch

 

2- Substitute the following recommendation in place of item # 3 since it will be easy to implement and should not be controversial.

       

 Restrict the amount of low votes from a single IP address within a certain time frame.  More specifically, only allow any IP to place a vote less than 4 once every 24 hrs.  We already have much of the logic to deal with the same time-lapse in dealing with votes from the same subnet that we can apply to this recommendation.

 

        The reasoning is based on the premise that people only low-ball the vote for more than one plugin at the same time as an act of malice.  This option will not restrict anyone from casting a "1" vote at any time;  they just would have to wait 24 hrs to cast the next "1-3" for the next plugin.  Call it a cool down period. 

 

We discussed the logic for doing the same for high votes.  We agreed that people that vote "8-10" for more than one plugin do not do so for malicious reasons and as such doesn't require any special handling.

 

Please let me know if anyone has any concerns with this recommendation.

 

Maher Masri
President, Genuitec LLC
(Telephone) 888-267-4176 x 704
(Direct) 469-293-5747
www.genuitec.com

 

 

 

 

----- Original Message -----

From: Ian Skerrett

Sent: Sunday, September 03, 2006 2:08 PM

Subject: [inbox] [phoenix-epic-dev] Current Votes for EPIC Themes and Priorities

 

All,

 

Attached is a consolidate view of the current voting for the Themes and Priorities.   Jochen, Eric, Todd and Howard you have still not voted.   If you could do so it would be great; below are the Themes and the “rules”.  If you do not plan on voting, can you please let us know.

 

Thanks

Ian

 

 

 

Ian Skerrett

Director of Marketing

Eclipse Foundation, Inc.

Tel: 613-224-9461  ext. 227

Fax: 613-224-5172

ian.skerrett@xxxxxxxxxxx

http://www.eclipse.org

Blog: http://ianskerrett.blogspot.com/ 

 

 

 

 


From: phoenix-epic-dev-bounces@xxxxxxxxxxx [mailto:phoenix-epic-dev-bounces@xxxxxxxxxxx] On Behalf Of Ian Skerrett
Sent: August 28, 2006 9:22 AM
To: 'The EPIC component of Phoenix'
Subject: [phoenix-epic-dev] EPIC Themes and Priorities

 

All,

 

Based on last Thursday’s call, I took the action item to draft a proposed set of Themes and Priorities.   Based on this strawman people can provide feedback on prioritization of the items.  If you think I have missed something, please feel free to add it.

 

I'd like to stress that this is a high-level document, not meant to provide specific agreement on implementation details.   At this time I think we should focus on the high-level themes, not the actual implementation.  I have also tried to attach a measurable metric to each theme, so we can understand what success is?

 

I believe the next steps are for people to provide feedback on the priorities.   I would suggest that for each theme you rank it +1, -1 or 0. +1 means you think it needs to be implemented in the next 6 months; -1 means it does not need to be implemented in the next 6 months; and 0 means if we have time and resources,  lets try to implement it.   To make the process more challenging, I would suggest that each person can only use four +1 votes.

 

 

High-level Themes and Priorities

 

1. Theme: Improve Usability for users of EPIC to make it easier to find/search plug-ins and relevant information

Goal: Should be able to go from the home page to a specific plug-in in two clicks.

 

2. Theme: Re-design home page to provide more emphasis on plug-ins

Goal: Emphasis of home page should be less news and forum focus and more on content (ie. plug-ins and services)

 

3. Theme: Add services/training component to EPIC

Goal: Have 10 services/education providers listed on EPIC by end of 2006

 

4. Theme: Increase visibility of Member plug-ins

Goal: Raise the level of visibility/awareness of plug-ins that are from member companies.  This should lead to additional traffic for member plug-ins and additional members listing their plug-ins

 

5. Theme: Increase number of plug-ins / Provide view of plug-ins from multiple sources

Goal: By end of Q1 2007 EPIC should have 900 plug-ins listed

 

6. Theme: Add organization view to EPIC

Goal: Add the ability to view EPIC content by organization.  Currently you can only view by plug-in listing.

 

7. Theme: Make it easier to use EPIC with the Eclipse update manager

Goal: Provide a listing of update sites that are related to the plug-ins listed on EPIC

 

8. Theme: Encourage other contributions to EPIC from other community members

Goal: Have new individuals contributing resources that extend the capabilities of EPIC

NOTE: I would suggest we include things like Job Posting, Speaker Center and Partner Program items listed on the wiki

 

9. Theme: Increase traffic to EPIC

Goal: Increase traffic to EPIC by 20% by the end of 2006

 

10. Theme: Outreach Programs

Goal: EPIC would enable the creation of topical communities who desire to form a community, network with other individuals of similar interest and values.

 

 

 

 

Ian Skerrett

Director of Marketing

Eclipse Foundation, Inc.

Tel: 613-224-9461  ext. 227

Fax: 613-224-5172

ian.skerrett@xxxxxxxxxxx

http://www.eclipse.org

Blog: http://ianskerrett.blogspot.com/ 

 

 

 

 

 


_______________________________________________
phoenix-epic-dev mailing list
phoenix-epic-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/phoenix-epic-dev


_______________________________________________
phoenix-epic-dev mailing list
phoenix-epic-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/phoenix-epic-dev

Back to the top