future plans

jlutes · 09-01-2011, 03:39 PM

I'm sure this post isn't in the correct place - which is part of my topic...

I've seen some desires for future features of Calibre. For instance, using a database that will support multiple client access, multiple user logins with different permissions, etc. I'm sure there is a punch list of suggested features that has some sort of ranking or perhaps a "in the works" indicator? Where would I go to see it or make suggestions?

Also, might I suggest Chaley or one of you other higher-ups expand the information available in the stickies? For instance, the sticky in the development sub-forum says what it isn't for but perhaps that could be improved? Perhaps instead of saying "this is not the place for bug reports" you should say "this is not the place for bug reports, but <this> is"?

theducks · 09-01-2011, 04:01 PM

Quote:

Originally Posted by jlutes

I'm sure this post isn't in the correct place - which is part of my topic...

I've seen some desires for future features of Calibre. For instance, using a database that will support multiple client access, multiple user logins with different permissions, etc. I'm sure there is a punch list of suggested features that has some sort of ranking or perhaps a "in the works" indicator? Where would I go to see it or make suggestions?

Also, might I suggest Chaley or one of you other higher-ups expand the information available in the stickies? For instance, the sticky in the development sub-forum says what it isn't for but perhaps that could be improved? Perhaps instead of saying "this is not the place for bug reports" you should say "this is not the place for bug reports, but <this> is"?

I believe it is on the To Do list

One basic rule is never tell the users what you are thinking about or you get buried in: "When's"
Calibre is complicated enough, that one tiny change affects a LOT of code

. Making it multi-user needs lots of under-laying support to prevent damage or clashes .

user_none · 09-01-2011, 05:00 PM

Development happens on a when we feel like it basis. What may sound fun today might quickly be dropped tomorrow for something else. There is no formal list because we work on what we want when we want. Such a list would be ignored.

Not to mention a working on list will cause two issues. As theducks said people will ask incessantly for updates. It will give new developers the feeling that those aspects are untouchable because a senior person has their name on it.

If someone isn't activity working on it then it's fair game. If some is working on something that doesn't mean they wouldn't appreciate some help.

Manichean · 09-01-2011, 06:31 PM

Quote:

Originally Posted by jlutes

Also, might I suggest Chaley or one of you other higher-ups expand the information available in the stickies? For instance, the sticky in the development sub-forum says what it isn't for but perhaps that could be improved? Perhaps instead of saying "this is not the place for bug reports" you should say "this is not the place for bug reports, but <this> is"?

The best way to make suggestions for the stickies would be to open a thread proposing them. That allows people to discuss the suggestions, and we can edit the sticky according to the consensus.

kovidgoyal · 09-01-2011, 10:29 PM

As others have said, calibre development is free form. New features happen when someone scratches an itch. So having TODO/feature lists is rather difficult. I work on calibre mainly because it is fun, and not having laundry lists is a big part of why it is fun

Once in a while, a feature request will resonate with a calibre developer and get implemented, but there is no guarantee that will happen.

09-01-2011, 03:39 PM	#1
jlutes Connoisseur Posts: 52 Karma: 12 Join Date: Jul 2011 Device: none	future plans I'm sure this post isn't in the correct place - which is part of my topic... I've seen some desires for future features of Calibre. For instance, using a database that will support multiple client access, multiple user logins with different permissions, etc. I'm sure there is a punch list of suggested features that has some sort of ranking or perhaps a "in the works" indicator? Where would I go to see it or make suggestions? Also, might I suggest Chaley or one of you other higher-ups expand the information available in the stickies? For instance, the sticky in the development sub-forum says what it isn't for but perhaps that could be improved? Perhaps instead of saying "this is not the place for bug reports" you should say "this is not the place for bug reports, but <this> is"?

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
An email from iRiver re: future firmware plans	jupstin	iRiver Story	0	07-28-2011 03:53 PM
Plans for Plays?	Dr. Scoops	Amazon Kindle	2	12-27-2009 10:38 AM
Fourth of July Plans?	desertgrandma	Lounge	92	07-05-2009 04:05 AM
FBReader 0.7.1 and plans	MishaS	Reading and Management	1	11-29-2005 11:29 PM
Future Plans	Alexander Turcic	Lounge	1	03-10-2003 01:05 PM

09-01-2011, 05:00 PM	#3
user_none Sigil & calibre developer Posts: 2,487 Karma: 1063785 Join Date: Jan 2009 Location: Florida, USA Device: Nook STR	Development happens on a when we feel like it basis. What may sound fun today might quickly be dropped tomorrow for something else. There is no formal list because we work on what we want when we want. Such a list would be ignored. Not to mention a working on list will cause two issues. As theducks said people will ask incessantly for updates. It will give new developers the feeling that those aspects are untouchable because a senior person has their name on it. If someone isn't activity working on it then it's fair game. If some is working on something that doesn't mean they wouldn't appreciate some help.

09-01-2011, 10:29 PM	#5
kovidgoyal creator of calibre Posts: 45,609 Karma: 28549044 Join Date: Oct 2006 Location: Mumbai, India Device: Various	As others have said, calibre development is free form. New features happen when someone scratches an itch. So having TODO/feature lists is rather difficult. I work on calibre mainly because it is fun, and not having laundry lists is a big part of why it is fun Once in a while, a feature request will resonate with a calibre developer and get implemented, but there is no guarantee that will happen.

Advert

Advert