Re: Broken links
Broken for me too, even after a cache clear and force reload. Link on homepage is: http://s.apache.org/couchdb-easy-issues Redirects to an error page: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=12310780resolution=-1customfield_12310270=New+Contributors+Level+(Easy)sorter/field=updatedsorter/order=DESCsorter/field=customfield_12310270sorter/order=ASC Two screenshots attached... Jonathan Porta On Mon, Apr 16, 2012 at 9:10 AM, Mike Coolin mcoo...@techie.com wrote: Just checked with both browsers. Page still broken. - Original Message - From: Robert Newson Sent: 04/16/12 10:27 AM To: dev@couchdb.apache.org Subject: Re: Broken links Seems fixed now, I guess it was a JIRA-side error. On 13 April 2012 20:27, Robert Newson rnew...@apache.org wrote: Thanks, working on it. On 13 April 2012 20:41, Mcoolin mcoo...@techie.com wrote: Hello, On the main page couchdb.apache.org the do you want to help section the links for easy, medium, and hard fa to open. Thanks Mike -- Sent from my Android phone with mail.com Mail. Please excuse my brevity.
Re: Broken links
How about this: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+COUCHDB+AND+resolution+%3D+Unresolved+AND+%22Skill+Level%22+%3D+%22New+Contributors+Level+%28Easy%29%22+ORDER+BY+updated+DESC%2C+cf%5B12310270%5D+ASC Jonathan Porta On Mon, Apr 16, 2012 at 9:29 AM, Robert Newson rnew...@apache.org wrote: 100 points to anyone who can make a stable link to JIRA. I have the access to fix the website, feel free to contribute with working links. B. On 16 April 2012 16:26, Jonathan Porta rurd...@gmail.com wrote: Broken for me too, even after a cache clear and force reload. Link on homepage is: http://s.apache.org/couchdb-easy-issues Redirects to an error page: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=12310780resolution=-1customfield_12310270=New+Contributors+Level+(Easy)sorter/field=updatedsorter/order=DESCsorter/field=customfield_12310270sorter/order=ASC Two screenshots attached... Jonathan Porta On Mon, Apr 16, 2012 at 9:10 AM, Mike Coolin mcoo...@techie.com wrote: Just checked with both browsers. Page still broken. - Original Message - From: Robert Newson Sent: 04/16/12 10:27 AM To: dev@couchdb.apache.org Subject: Re: Broken links Seems fixed now, I guess it was a JIRA-side error. On 13 April 2012 20:27, Robert Newson rnew...@apache.org wrote: Thanks, working on it. On 13 April 2012 20:41, Mcoolin mcoo...@techie.com wrote: Hello, On the main page couchdb.apache.org the do you want to help section the links for easy, medium, and hard fa to open. Thanks Mike -- Sent from my Android phone with mail.com Mail. Please excuse my brevity.
Re: Broken links
I think it just needed to be url encoded? Jonathan Porta On Mon, Apr 16, 2012 at 9:36 AM, Jonathan Porta rurd...@gmail.com wrote: How about this: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+COUCHDB+AND+resolution+%3D+Unresolved+AND+%22Skill+Level%22+%3D+%22New+Contributors+Level+%28Easy%29%22+ORDER+BY+updated+DESC%2C+cf%5B12310270%5D+ASC Jonathan Porta On Mon, Apr 16, 2012 at 9:29 AM, Robert Newson rnew...@apache.org wrote: 100 points to anyone who can make a stable link to JIRA. I have the access to fix the website, feel free to contribute with working links. B. On 16 April 2012 16:26, Jonathan Porta rurd...@gmail.com wrote: Broken for me too, even after a cache clear and force reload. Link on homepage is: http://s.apache.org/couchdb-easy-issues Redirects to an error page: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=12310780resolution=-1customfield_12310270=New+Contributors+Level+(Easy)sorter/field=updatedsorter/order=DESCsorter/field=customfield_12310270sorter/order=ASC Two screenshots attached... Jonathan Porta On Mon, Apr 16, 2012 at 9:10 AM, Mike Coolin mcoo...@techie.com wrote: Just checked with both browsers. Page still broken. - Original Message - From: Robert Newson Sent: 04/16/12 10:27 AM To: dev@couchdb.apache.org Subject: Re: Broken links Seems fixed now, I guess it was a JIRA-side error. On 13 April 2012 20:27, Robert Newson rnew...@apache.org wrote: Thanks, working on it. On 13 April 2012 20:41, Mcoolin mcoo...@techie.com wrote: Hello, On the main page couchdb.apache.org the do you want to help section the links for easy, medium, and hard fa to open. Thanks Mike -- Sent from my Android phone with mail.com Mail. Please excuse my brevity.
Re: website jira
Does anyone think it would be a good idea to list the proposed changes/issues to/with the site and then have the community vote on them? Opinion: - I think the new site feels very much up to current design trends. - The current site far surpasses the previous's site delivery of the message: CouchDB is alive and ready for you to start using it! - I think the focus on the text keeps it simple and easy to understand. - The Quick Links listed under Development could be a good thing to have at the very top of the Want to Contribute? section. That way a person could jump right in instead of TL;DR'ing that section. Do we have the ability to tweak the themes of JIRA or the Wiki to have it better match the homepage? Jonathan Porta On Mon, Apr 16, 2012 at 1:30 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Mon, Apr 16, 2012 at 9:14 PM, Wendall Cada wenda...@83864.com wrote: I don't know if you guys care about my feedback, but I also do this stuff for a living. I've added my comments below. On 04/16/2012 10:35 AM, Noah Slater wrote: On Mon, Apr 16, 2012 at 6:26 PM, Benoit Chesneaubchesn...@gmail.comwrote: On Mon, Apr 16, 2012 at 7:13 PM, Noah Slaternsla...@tumbolia.org wrote: On Mon, Apr 16, 2012 at 5:04 PM, Benoit Chesneaubchesn...@gmail.com wrote: On Sun, Apr 15, 2012 at 10:45 PM, Noah Slaternsla...@tumbolia.org wrote: Benoît: Please don't add anything to the top navigation. The only thing I think we should add there is a link to the Quick Links section - but I already tried that and the auto-scrolling breaks. If you can figure out a way to make it not break, please add that. Well why not about a context menu? What? http://en.wikipedia.org/wiki/Context_menu here a menu that culd appear when you click on a top navigation link. Okay. No, I don't think we should have one of those. Agreed, these are problematic for touch devices. It's doable, but a royal pain in the ass. Bob: We link to the documentation in the Quick Links footer. The documentation itself includes the API reference. I don't think there's any particular need to link to the API reference on the page as a special call out. Benoît: I agree that I think the text is very big, but it's the only way we could get it looking good with the text stretched across the whole screen. Perhaps the thing to do is to shorten the width of the text some how. We need a designer to look at it. Why the text has to be stretched across the whole screen? It looks good but it's actually really painful to read it. Yes, I'm not sure what to do about it. We need a designer to look at it. i would first reduce the width to 40em (common width on desktop) and the font size to something human readable then look at a designer to make eventually things looking better (wich is far less important than readability). I can do that quickly if anyone is OK. I want a designer to look at this. It is readable enough that we don't have to take any emergency action. I am happy to wait for this to be picked up as CouchDB re-organises itself. The font size is perfect. Smaller, and I'll override locally to actually be able to read it. I have 20/20 vision, this size works for everything for me from my primary 24 monitor to my android phone. This is a bit wide for readability. For reference http://www.readability.com/articles/0hbffwvq#In regard to the font size on the readability link, I set text size to 120% by default, as it is far too small. This makes it exactly the same size as the default for couchdb landing page. Are you kidding ? Did you see my screenshot? beeing able to place only 10 lines of text in 1024x768 is far from perfect. larger text are know to be unreadable. This is absolutely not common to have a text that extend on all width and far from confortable. Hence the size of a book or a page. even ebooks. The links to the web interface for the mailing list are there. Click on the mailing list names themselves. Hard time to figure I had to click on the link. That's not intuitive. Intuition is relative. Do you mean we should encourage people to try all the link before finding the right content behind? None of these links clearly tell to the user that it links to a web interface. I disagree. I think the links are very clear. Where do you read this is a link to the web browsing interface? Having to click to know it show how well the text describe it. That not like i'm not using the web since a long time. Also I don't find the markmail link. Markmail is not official. But it was there and useful. So put it on the wiki. This is not what I'm asking. This site is about the bare essential facts about CouchDB. Let's keep it simple. I don't really see how it's related. Or rather how it's not related. Not convinced this is a big deal. How many people use the web interface to our mailing lists by clicking
Re: website jira
I agree regarding the differing use cases. That is the problem exactly. I am not sure you could make a site that follows today's trends of less is more and creative simplicity that also fully caters to the users, fully caters to the developers and fully caters to the potential/new users. That a lot of content, not to mention several different web applications, to try to cram into one webpage. One thing worth pointing out is that contributing takes a higher level of commitment on the user's part than does researching/trying CouchDB. Someone willing to contribute would probably put up with having to spend a few extra minutes the first time they decide to contribute. Subsequent visits are probably going to be via bookmarks/direct entry vs looking for the link on the project homepage. Basically, someone willing to contribute to the project will probably put up with more hassle the first time than someone only interested in trying it out. Unfortunately, this seems a bit backwards in the whole customer service mentality where you focus on taking care of your valuable customers. But I think it makes sense to gear the site toward newer/potential users in order to grow the user-base which will eventually grow the number of contributors anyway. Jonathan Porta On Mon, Apr 16, 2012 at 4:30 PM, Eli Stevens (Gmail) wickedg...@gmail.comwrote: I think that much of the disagreement stems from different audience / use cases in mind when proposing changes to the web site. I see a few main user profiles that visitors to the website could be lumped into: - Neophyte users who are looking for information about CouchDB to see if it interests them; install it for the first time; upload first data; write first view; etc. - Slightly more experienced users who are looking for support; either they have a question not answered by the docs, they've found a bug they would like to report, etc. - Contributors to the project, looking to do whatever it is they're wanting to do today. Looking at it from the outside, I would say that the website simply can't meet the needs of both the first and the last group well at the same time. The use cases are just too different. Also, since I think that there are at least an order of magnitude more potential users than there are actual users, and there's another order of magnitude more users than there are contributors, if you want the most impact, the website needs to target potential users first and foremost, while throwing a bone or two to current users, and totally ignoring contributors (because honestly, you guys did fine with the old website, and I'd bet a dollar none of you needs to have a link to click on to get to JIRA; it's in your history, bookmarks, or is your homepage ;). I understand the motivation to try and get more contributors to help the project progress, but I think that getting more users and letting the contributors come organically will be much more sustainable than going after contributors directly. I could be wrong. Either way, figuring out the target audience will probably make a lot of these do we need a link to JIRA; should it be called JIRA or Issues questions have obvious answers. Cheers, Eli On Mon, Apr 16, 2012 at 1:15 PM, Miles Fidelman mfidel...@meetinghouse.net wrote: Jonathan Porta wrote: Does anyone think it would be a good idea to list the proposed changes/issues to/with the site and then have the community vote on them? Yes! Opinion: - I think the new site feels very much up to current design trends. - The current site far surpasses the previous's site delivery of the message: CouchDB is alive and ready for you to start using it! - I think the focus on the text keeps it simple and easy to understand. - The Quick Links listed under Development could be a good thing to have at the very top of the Want to Contribute? section. That way a person could jump right in instead of TL;DR'ing that section. Seems to me that there are some fairly standard things that people look for along the top of a software-related web page, that are conspicuously missing from the CouchDB page, unless you go digging at the bottom of the page or by clicking through links. A fairly common list is: - About (or Learn More) - missing - Downloads - Documentation - missing - Support - missing - News (or Blog) - missing - Development - missing (Contribute is ambiguous) - Community - missing (admittedly Mailing Lists is there, but what about links to unofficial archives, other Couch related sites, .) - Events - Demo - Facebook and/or Twitter I'd take a look at other sites, like erlang.org, drupal.org, mongodb.org , and so forth. -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra
Re: website jira
Having worked on projects that were decided by a committee, I agree. I think I suggested that due to the fact that I am not a contributor and that I have only been using CouchDB for a few months and am not fully sure yet how things are decided within the community. Please excuse my ignorance on this one. Jonathan Porta On Mon, Apr 16, 2012 at 5:07 PM, Noah Slater nsla...@tumbolia.org wrote: Some comments. I wish it could have been discussed before too. Sorry to jump on you here Benoît, but this is not the way CouchDB works. And every time I see this unhealthy attitude raise its ugly head, I am going to stamp on it. CouchDB operates a culture of trust. We trust that community members are going to act in the interests of the project. Whatever you want to do, just have at it. It is easier to ask for forgiveness than it is to get permission. The only rule to that is: don't be a berk! This permission culture that we seem to have fostered in recent years is a blight on the project, and it is my hope that we can use recent events to shake it off. But we need to start by stamping it out where ever we see it. Setting an example. The website was not discussed prior to the launch, because I can tell you right now, with my hand on my heart, it would never have seen the light of day. We'd still be sat here, with a 5 year old site, moaning about it. Because everyone thinks they know how to design, and everyone has an opinion, and the thing would've been debated until it was killed. You can imagine how much I flinched when I read this: Does anyone think it would be a good idea to list the proposed changes/issues to/with the site and then have the community vote on them? Not picking on you here Jonathan, but it's a good example of what I am talking about. Voting on the design of the site is probably THE worst idea possible. If we want a site that looks good, then we need to entrust a single individual (preferably with a good eye for design, and modern design skills) to own the site, and to take responsibility for any changes. That is the only way we will avoid the dreaded design by committee, and it is the only way we will be able to sensibly evolve our brand. So, I am asking people now. Please do not touch the design of the site unless you are prepared to take ownership of the design of the site. And I mean complete ownership. If you want to mess with the design, please be prepared to take further requests. This is not to discourage you. In fact, quite the opposite. If someone wants to do this, I would be overjoyed! But we need someone who is committed, and who can use their single, unified vision to guide us in the right direction. Are you a designer? Do you think you could help to maintain our one page static HTML website? Please get in touch. We need your help! In the mean time chaps, I have created a wiki page to collect our ideas. http://wiki.apache.org/couchdb/Website_Design
Re: Wikipedia article cleanup
Any better with this: Apache CouchDB, commonly referred to as CouchDB, is an open source NoSQL database that uses JSON for documents, JavaScript for MapReduce queries, and HTTP for an API.[1] CouchDB was first released in 2005 and later became an Apache project in 2008. Unlike in a relational database, CouchDB does not store data and relationships in tables, but instead stores structured data as JSON documents. CouchDB implements a form of Multi-Version Concurrency Control (MVCC) in order to avoid the need to lock the database file during writes. Conflicts are left to the user to resolve. Other features are ACID semantics with eventual consistency, MapReduce, incremental replication and fault-tolerance. CouchDB ships with Futon, a web based administration console. Jonathan Porta On Sat, Apr 14, 2012 at 12:09 PM, Robert Newson rnew...@apache.org wrote: Certainly very crufty in places. The Talk page contains unchallenged (and untrue) assertions that we're all moving to Couchbase server too! B. On 14 April 2012 16:46, Noah Slater nsla...@tumbolia.org wrote: Hey, Does someone want to take a look at the CouchDB Wikipedia article? The opening paragraph is terrible: Apache CouchDB, commonly referred to as CouchDB, is an open source document-oriented database NoSQL database system. It could be considered similar to MongoDB. A document-oriented database NoSQL database system? What. We should also not be compared to MongoDB in the first sentence. Or again, later in the article. It should be sufficient to let CouchDB stand on its own merits. Much like how the MongoDB article does not make constant comparisons with CouchDB. There are a number of factually incorrect statements that need cleaning up too. Like the statement that Damien Katz is our lead developer. It should, instead, be noted that he retired from our PMC. Also, IBM do not directly financially support the project, nor do any other companies. Individual developers are not sponsored either. The only sponsorship our project has is listed on the ASF sponsorship page. http://www.apache.org/foundation/thanks.html There are a few other problems too, like outdated references to Couchbase and UQL. In general, there is probably a lot of love and attention someone could pour in to this. I notice that it was updated last week to include the new version number. So someone presumably has their eye on the article. We just need a little bit more work putting in to it, I think. I would do this myself, but I worry that I have a strong conflict of interests. Anyone calm and rational and distant enough want to take this on? Thanks, N
Re: [VOTE] Apache CouchDB 1.2.0 release, second round
Fedora 15 64bit, Erlang 14B04, Spidermonkey 1.8.5 Everything checks out! Jonathan Porta On Fri, Feb 24, 2012 at 3:44 AM, Dirkjan Ochtman dirk...@ochtman.nl wrote: On Thu, Feb 23, 2012 at 00:28, Noah Slater nsla...@tumbolia.org wrote: We are voting on the following release artifacts: http://people.apache.org/~nslater/dist/1.2.0/ Gentoo Linux 64-bits, Erlang 13B4, Spidermonkey 1.8.5. Signatures check out, make check passes. Browser tests pass in Firefox 12.0a2, although replicator_db_security failed once before it succeeded. +1 on release. Cheers, Dirkjan
Re: [VOTE] Apache CouchDB 1.2.0 release, second round
+1! Jonathan Porta On Fri, Feb 24, 2012 at 7:07 AM, Sebastian Cohnen sebastiancoh...@googlemail.com wrote: Jonathan, you forgot to cast your vote! (Which needs to be either +1 or -1) On 24.02.2012, at 14:50, Jonathan Porta wrote: Fedora 15 64bit, Erlang 14B04, Spidermonkey 1.8.5 Everything checks out! Jonathan Porta On Fri, Feb 24, 2012 at 3:44 AM, Dirkjan Ochtman dirk...@ochtman.nl wrote: On Thu, Feb 23, 2012 at 00:28, Noah Slater nsla...@tumbolia.org wrote: We are voting on the following release artifacts: http://people.apache.org/~nslater/dist/1.2.0/ Gentoo Linux 64-bits, Erlang 13B4, Spidermonkey 1.8.5. Signatures check out, make check passes. Browser tests pass in Firefox 12.0a2, although replicator_db_security failed once before it succeeded. +1 on release. Cheers, Dirkjan
Re: JIRA Bots
+1 Jonathan Porta On Tue, Feb 21, 2012 at 10:54 PM, Paul Davis paul.joseph.da...@gmail.com wrote: Can whoever designed the Sam Bisbee JIRA bot (what an odd name choice) figure out if its possible to tag emails somehow to give me a filter criteria to add a label for closing old ass bugs or something? (Awesome work on JIRA processing Sam!)
Re: Any experts care to answer this SO query?
Hi Roger, To agree with your comment, I thought CouchDB was dead/dying until I joined the mailing lists. I think CouchDB just needs to sell itself a bit better, and somehow break out of how it is currently lumped in with (perceptually) to Couchbase products. Thanks for the suggestion. Prior to deciding I wanted to use CouchDB, I have been using a post queue that I wrote. It's a service that responds to connectivity events and persists the transactions in the queue when it is in the correct state. My app just adds transactions to it via the post queue service's API. The transactions are just JSON strings. It works really well for persisting data from the mobile device to the server. But, it doesn't cover the other side of sync - pulling data from the server. I thought if I could be running CouchDB on the Android device, I can let the data eventually replicate, resulting in the mobile device having it's needed data, and the server eventually getting what the mobile app collected. Do you know anything about Mobile Syncpoint? Jonathan Porta PO BOX 21365 Billings, MT 59104 On Mon, Feb 20, 2012 at 2:10 AM, roger.moff...@gmail.com wrote: I'm so glad I'm not the only person finding it awesome but frustrating! I'm currently scheduled to give a talk on couchdb for mobile (specifically ios) in London but just know that the QA is going to be full of 'isn't couch dead / isn't everyone using mongo now' type questions. To look at your specific question on Android - have you considered an alternative architecture where you persist couch objects locally and then sync each object to the remote database when required? It could well be that your use case requires a heavier client side solution, but for the projects I'm working on I find this works really well when the number of objects in flight at any one time is low. I basically deserialise documents into custom objects which are persisted client side and then serialised on the way out again. I get the real benefit of couch when it comes to searching (I have some entertaining views) and also storing photos etc as attachments and in my case I can restrict this to being when the user is online. Obviously this approach is a compromise and may not be suitable for your use case. TouchDB looks like a really interesting option too ... although maybe not production ready yet. https://github.com/couchbaselabs/TouchDB-iOS Roger If anyone wants to give me word on whether Couchbase Mobile Syncpoint is the route I should go for Android, I would appreciate it! Still trying to figure this out! ;) Jonathan Porta
Re: Couchbase trademark issues
I know that I am new around here, but, I will still hand out my opinion, which is not legal advice. :) CouchDB is a brand, just like Apple, Google and countless others. If you a person is involved with the project, it is likely that the branding is not going to strongly influence their decisions to use or not use the product. If, however, a person lacks any pre-existing relationship with a brand, that individual is going to be greatly influenced by the presence of similar/confusing brands in the marketplace. Arguably, this causes immeasurable harm to a brand's image as well as it's adoption in the community. Great software like CouchDB exists to be shared and adopted by others. Anything that, intentionally or unintentionally, limits those abilities is quite harmful to the project. It seems like Couchbase is eliminating some of the confusion by consolidating their product line. I would be interested to see what legal has to say about it. It would also be a good idea to see what can be done in conjunction with Couchbase to help eliminate these issues. They publicly acknowledged the confusion [1], so, they may be willing to work on a solution. [1] http://blog.couchbase.com/couchbase-2011-year-review Jonathan Porta On Mon, Feb 20, 2012 at 4:19 AM, Noah Slater nsla...@tumbolia.org wrote: On Mon, Feb 20, 2012 at 10:54 AM, Dirkjan Ochtman dirk...@ochtman.nlwrote: +1, but we/you should probably try to be non-confrontational about it. Just to clarify, based on this, and some off-list feedback. I'm not asking for legal advice, that's what the legal list is for. They very well may turn around and say that we have not a leg to stand on. I was asking what other people feel about the issue at hand. There is obviously an issue. But how important is it and what should we do about it? Is it a short-term problem? If that's the case, community and good-will might be our tool. Or is it a long-term problem? In which case, we might want to consider other, more direct, measures.
Re: Couchbase trademark issues
Something interactive that shows off CouchDB a bit would be awesome. Immediately, I am thinking about what I saw earlier on Redis: http://try.redis-db.com/ I am not saying that would be the best fit or that it would be a good idea to copy it. Just wanting to throw out some ideas. Jonathan Porta On Mon, Feb 20, 2012 at 5:09 AM, Robert Newson rnew...@apache.org wrote: 1 for a revamped couchdb.apache.org. The most recent change, I think, was mine, which simply dropped the misleading diagram in the top-right. Long past time for an overhaul. Who has the time and skill to make this happen? B. On 20 February 2012 12:02, Simon Metson simonmet...@googlemail.com wrote: Hi, I was asking what other people feel about the issue at hand. There is obviously an issue. But how important is it and what should we do about it? Is it a short-term problem? If that's the case, community and good-will might be our tool. Or is it a long-term problem? In which case, we might want to consider other, more direct, measures. I think there is a short term fix to some of these issues. As the original post says when you go to the apache project page you see a very stale project page. I know this has come up time and again but fixing that seems to be a fairly easy thing to do (and should be done regardless of the wider issues) and would help alleviate some of the confusion. I appreciate the let the code speak for itself response that came after Damien's departure but that only works for people already engaged with the community. For new users (or users not so involved) it's a PR disaster IMHO. Having a clear message about what CouchDB is and how it (doesn't) relate to Couchbase on the front page seems necessary, and might help matters while wider issues are resolved. What needs to be done to close that out and how can I (and others) help? Also, the Hadoop guys have quite a nice page: http://wiki.apache.org/hadoop/Defining%20Hadoop. If we apply the same reasoning as that I'd say Damien's original post would probably fall under inappropriate use, and Couchbase as a competing product possibly does too (c.f. Hadooping the motor industry) Cheer Simon
Re: Any experts care to answer this SO query?
and Node.js seem to do a better job at this, maybe some ideas can come from their approach. /rant It all boils down to: 1. How can I incorporate CouchDB into my Android project, and replicate with a CouchDB instance elsewhere? 2. What can I do to help CouchDB make things easier for someone like me to adopt CouchDB? More specifically, what is there that the project team would allow me to help with in this area? I really really like the CouchDB project, but, I can't see how it will continue to be a viable solution if newcomers to the technology encounter issues similar to what I have encountered. Jonathan Porta PO BOX 21365 Billings, MT 59104 On Sun, Feb 19, 2012 at 9:58 AM, roger.moff...@gmail.com wrote: I think this question on stack overflow expresses a lot of the confusion in the marketplace about the current direction of couchdb. I hope you'll forgive me posting this to the dev group, but as a couch evangelist myself, I share Jonathan's pain. http://stackoverflow.com/questions/9343868/confused-on-how-to-use-couchdb-on-android I am feeling a bit more confident about the future of couchdb having seen the activity in this forum over the past week. However I feel, looking from the outside in, that the project does have a perception problem. The problem I think largely stems from the fact that there is nothing on this page that reflects the online discussions that arose following Damien's departure. http://couchdb.apache.org/ So when you are searching for information on couchdb, you tend to see a very stale project page, and then lots of much more recent online posts elsewhere asking if couch is dead now that the founder has left. I know there is a lot of sensible and sane discussion on other blogs, but I really feel that the apache couchdb pages need to address the matter head on and inform the community better as to the future. As an aside, the decision to rebrand membase as couchbase has, in my opinion, done untold damage. This is the real issue behind the confusion and is something I think the couchdb project needs to work on. I'm happy to help where I can ... I love couch and use it as the backend for many of my mobile projects. Having a restful database that talks JSON is such a perfect fit for so many applications that really, couchdb should be storming ahead of other nosql options and yet I find myself having to work harder and harder to justify its use over (say) mongo. The reason I am having to work harder is purely a perception problem and hence I feel this is the area that needs a bit more work! All that said, I'm so glad I joined the dev group last week, it's given me a lot more confidence that things are moving in a positive direction ... Roger
Re: Any experts care to answer this SO query?
No problem. I hope it wasn't too much of a rant. It's just that CouchDB is an awesome project, but, I am not sure other new comers will be as persistent as I have. Once I wrap up my first CouchDB deployment in a few days, I will contribute some helpful information to the Wiki. I have editing privileges as of yesterday. If anyone wants to give me word on whether Couchbase Mobile Syncpoint is the route I should go for Android, I would appreciate it! Still trying to figure this out! ;) Jonathan Porta On Sun, Feb 19, 2012 at 2:24 PM, Noah Slater nsla...@tumbolia.org wrote: Thank you for this Jonathan, it has been very helpful for me. I've flagged the email and I'll review it again when I'm putting together a plan for the new website. The wiki, as always, could do with some love. If you have a bit of spare time, it would be cool if you could fix up any of the things you think are confusing. Just let me know your account and I'll give you edit access. On Sun, Feb 19, 2012 at 6:45 PM, Jonathan Porta rurd...@gmail.com wrote: Roger, thanks for posting that! Being new to this community, I have spent more time confused than any other time I have picked up a new technology. The confusion primary stems from the multitude of Couchbase products that everyone talks about, coupled with the fact that (seemingly) all of the online content about CouchDB was written by people who now work at Couchbase. The difference in appeal between Couchbase's website and CouchDB's website is huge. My initial thoughts were that CouchDB was mostly abandoned as an Apache project, and that Couchbase was leading the charge in further development. This misconception lead me to wasting a lot of time with Couchbase Server, only to find out that everything I just learned in the two O'Reilly books I just bought was mostly wrong, as it did not apply to CouchDB. Basically, Couchbase Server is Membase with a confusing name. Recovering from that mistake, I then stumble across Damien's blog post about The future of CouchDB: Couchbase. At this point, I am ready to give up. I have spent days trying to figure out a new technology that sounds incredible, but, I have not had any success. To further show how hard it was to get to where I am now, here is how I started down this road: I easily found this talk done by J. Chris Anderson: http://www.youtube.com/watch?v=-9C2x54Of-M This got me pretty excited about the mobile CouchDB offering, yet, I couldn't find much more information until I just Googled J. Chris Anderson CouchDB. This is how I discovered Couchbase, the company. Seeing that J. Chris works there, I assumed Couchbase Server was a distribution of CouchDB. I was wrong. In the past when I have had issues like this, it is usually cleared up by reading through the Wikipedia articles on the subject. As of the last time I checked, the articles on Wikipedia were not very helpful in understanding the differences between Couchone, Couchbase, CouchDB, CouchApp, Couchbase Single Server, Couchbase Mobile Syncpoint, etc. Here is the internal dialog going on in my head: I finally found what I *think* might be the coveted CouchDB Android: http://www.couchbase.com/wiki/display/couchbase/Couchbase+Mobile+Syncpoint Stop right there! There are two different products on that page? Couchbase Mobile Syncpoint and TouchDB. TouchDB sounds like it is even further away from CouchDB, so I am not going to look at that. At least the Couchbase Mobile Syncpoint has the word Couch in it, so, maybe that is what I want? Though, I just wasted a bunch of time with Couchbase Server, so I am a little weary of looking at something with the Couchbase name stuck on it. I know it doesn't work with CouchDB, and doesn't have a REST API. Again, I was wrong! I guess Couchbase Mobile Syncpoint is compatible with CouchDB, according to the Couchbase HTTP API Documentation (Am I missing the joke here?) I end up on this page: http://www.couchbase.com/wiki/display/couchbase/Android - All is going well until I see Couchbase HTTP API Reference - http://www.couchbase.com/docs/couchbase-api/index.html - Couchbase doesn't have an HTTP API...I click that link. The title says: Couchbase, yet, the rest of the document says CouchDB It's like a case of find+replace gone wrong. So... Is this the API for Couchbase, CouchDB, or Couchbase Mobile Syncpoint? Where is the API for Couchbase Mobile Syncpoint, that was, after all, the product page I was just on. The document never mentions Syncpoint. The CouchDB Wiki isn't much help either. Here is the first thing I see on the Android page: These instructions are outdated So, I follow the link - https://github.com/couchbase/Android-Couchbase-SourceBuild - there are no instructions on how to use this. No links to instructions. At this point, I am starting to think that maybe everyone just gave up on the Android port. Why can I find loads of posts
