Difference between revisions of "OSBW Statement of Interests"
Johnmiedema (Talk | contribs) (New page: Statement of Interests - wide open list of things that interest people) |
Johnmiedema (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | + | [[Open_Source_Book_Widgets|OSBW Main Page]] | |
| + | |||
| + | A number of people have expressed an interest in collaborating on open source book widgets. It makes sense to pool resources, but doing so takes a bit of coordination. An easy place to start is to collect a list of general interests in open source book widgets. | ||
| + | |||
| + | Please provide a short statement of your interest in open source book widgets. What brought you here? What would you like to see come out of this? Any ideas about where collaboration is needed in particular? Please include your name with your statement. | ||
| + | |||
| + | === Shared Modules === | ||
| + | |||
| + | Why reinvent the wheel? Many book widget designers are interested in similar things: show book covers and other book data, use COinS or unAPI for integration with other applications, show availability, etc. My OpenBook plugin works in WordPress but much of the code can easily be adapted for other environments. As I move forward with OpenBook development, I would like to move the non-WordPress-specific code into code modules that can be shared with WordPress and non-WordPress widgets/plugins/modules. If others do the same, we can reduce effort. John Miedema | ||
Revision as of 12:56, 12 January 2009
A number of people have expressed an interest in collaborating on open source book widgets. It makes sense to pool resources, but doing so takes a bit of coordination. An easy place to start is to collect a list of general interests in open source book widgets.
Please provide a short statement of your interest in open source book widgets. What brought you here? What would you like to see come out of this? Any ideas about where collaboration is needed in particular? Please include your name with your statement.
Why reinvent the wheel? Many book widget designers are interested in similar things: show book covers and other book data, use COinS or unAPI for integration with other applications, show availability, etc. My OpenBook plugin works in WordPress but much of the code can easily be adapted for other environments. As I move forward with OpenBook development, I would like to move the non-WordPress-specific code into code modules that can be shared with WordPress and non-WordPress widgets/plugins/modules. If others do the same, we can reduce effort. John Miedema
