Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] [GSOC 2012] Milestone Plan for project Enhancing Salvo Newsreader
Hi wim,
I did some research on this. But need to do more. Also I talked with my mentor. According to what I understood We can facilitate this by designing a generic connectivity API with methods fo example like Connect(), Disconnect() and using parameters to invoke the relevant implementation for the request. To do this I should first study about such protocols and deign the API very carefully clarifying all necessary parameters.
Your opinions are highly valued.

Regads,
tishan

On Mon, May 28, 2012 at 1:04 PM, tishan pubudu kanishka dahanayakage <dtishanpubudu@xxxxxxxxx> wrote:
Hi Wim,
Thanks for your feedback. I will update the milestone plan according to your suggestion and I will also talk with my mentor regarding changes.
Still I am not in a position to suggest an abstraction for newsgroup. So I will straight away start by researching about NNTP dependency in Salvo and will contact you if I come across any problem.

Thanks,
Tishan


On Mon, May 28, 2012 at 4:01 AM, Wim Jongman <wim.jongman@xxxxxxxxx> wrote:
A central class in the NNTP model is the INewsgroup interface [1]. A newsgroup is typical NNTP lingo. So the question is, how can we make this abstract: 

In bugzilla, you can argue that a Newgroup is some combination of "Product" and "Component" [2] 
In fudforum, the mapping to a newsgroup is a "Forum" [3]
In Facebook, the newsgroup is the account
etc ...






[3]  http://cvs.prohost.org/index.php/FUDAPI 

On Mon, May 28, 2012 at 12:20 AM, Wim Jongman <wim.jongman@xxxxxxxxx> wrote:
Hi Tishan,

Thank you for the plan. I think M7, M8 , and M10 are the more significant items. So I recommend that you place them on the list first. Notifications are nice but not very important. In fact I would start with M10 since that was the whole idea of the project in the first place. 

What M10 should be able to do:

Salvo is there to discuss something. It was originally intended to provide a workbench gui on the Eclipse news server. Around the time of Salvo's first version, the webmaster "replaced" nntp with a new webbased forum (FudForum) (which luckily is able to cross-post to NNTP and until this date still does).

So the question was: continue with NNTP support _or_ switch to FudForum API [1]. Of course, this scenario is not correct, instead we should look for an abstract connection to ANY discussion structure: M10. 

Salvo can be split into three major parts: 

1. the gui
2. the local store
3. the connection to nntp

The Store API is already decoupled from any specific technology[2] with two implementations, Derby and File system of which File system is incomplete/broken (M7).

The server part of the API is sort of fixed on NNTP [2]. However, it should be possible to make an implementation that does not rely on NNTP but still the term NNTP is used frequently in the API [2]. You should look how the API can be enhanced so that it does not tie to NNTP anymore, rewrite the NNTP implementation to follow the new API and make a new implementation to prove that the decoupling works. (for instance to bugzilla or to fudforum)


  

On Sun, May 27, 2012 at 9:50 PM, tishan pubudu kanishka dahanayakage <dtishanpubudu@xxxxxxxxx> wrote:
Hi Harshana, Scott, Markus, and Wim,

Here is the milestone plan for my GSOC project 'Enhancing Salvo Newsreader'

Plan       

M1:Deliver Enhanced notifications for own posts            May 31

M2:Provide developed notification count                        June 6

M3:Deliver developed notification list                            June 17

M4:Linking notification to the relevant article.                June 24

M5:Implement functionality for user defined filters.        July 4

M6:Deliver unread post counter for filters.                     July 10

M7:File system store completion                                  July 28

M8:Enhanced article view                                            August 12

M9:Produce documentation of project                          August 18

M10:Provide NNTP independent Salvo product               Optional

Milestones

M1:Deliver Enhanced notifications for own posts

Completion of this milestone will provide a special notification for users own posts. This notification will be shown in a different color and it will blink.

M2:Provide developed notification count

This milestone will deliver a notification pop-up where it will show the show the number of missed notifications.

M3:Deliver developed notification list 

Completion of this milestone will provide a notification list where notifications will be viewed prioritized by the received time. 

M4:Linking notification to the relevant article.

This milestone will deliver a notification pop-up which will direct user to relevant article when a user click on a notification.

M5:Implement functionality for user defined filters.

Completion of this milestone will provide an option to users to define custom filters in th news digest view so that posts will be grouped into those filters.

M6:Deliver unread post counter for filters.

This milestone will deliver a unread post counter for each user defined filter.

M7:File system store completion

This milestone will deliver a fully functional file system store which includes all the functionality resides in Derby store.

M8:Enhanced article view

Completion of this milestone will deliver a bug free, more stable and user friendly article view.

M9:Produce documentation of project

This milestone will provide complete set of documentation of the project.

M10:Provide NNTP independent Salvo product 

Currently Salvo product depends on NNTP. Completion of this milestone will provide a NNTP independent Salvo product.  


Note: Milestone plan will be updated as the project goes on. I will make the milestone plan available in the project wiki [1] and will do the relevant changes there. Also M10 will be implemented within the GSOC program if the time permits. Else I will look into it personally.


Your comments are valued.

Regards,
Tishan



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




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



Back to the top