semanticscuttle-devel — General discussion about SemanticScuttle development

Re: [Semanticscuttle-devel] regarding "help wanted" post / a first task

[Christian W. <cw...@cw...>]

Hi Golanor,



> ok, I subscribed to the mailing list and got the code from git.

The first - easy - task for you to solve could be bug #3097187 [1]

The steps to take are:
1. Find out what the things are needed to do to implement the feature
2. Look at the code and see what needs to be done where to do it (this
   might be a bit overkill for that bug, but it is important when
   implementing new features)
3. Write that up and send it to the mailing list. We can discuss it
   then
4. Create your own feature branch (i.e. "fix-twoword-opensearch")
   from master and implement it in there
5. Push the branch to sourceforge so I can review it.
6. If everything is fine, I will merge it into the master branch

Please consider the following things:
1. SemanticScuttle tries to follow the PEAR Coding Standards. Use the
   PHP_CodeSniffer tool from PEAR to make sure you don't leave more
   style errors than there were when you began working on the file. Not
   all files comply to the styles yet, but we're on the right track
2. We have unit tests. Run them. Make sure that they still work when
   you finished your task. Better: Write a test for your own bug first
   - it should fail. Then fix the bug, and your test should work now.
3. If you find other bugs, open a bug report.
4. Do not fix several things in one branch. This really makes it hard
   to merge changes into the master branch. Creating a new branch in
   git is cheap, so use that.
5. Update the Changelog
6. I repeat myself, but: Only commit in your own branches.


[1]
https://sourceforge.net/tracker/?func=detail&atid=1017430&aid=3097187&group_id=211356

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-

Re: [Semanticscuttle-devel] Fix bugs, implement feature requests

[Brett D. <bs...@fr...>]

Thanks.

On Fri, 28 Jan 2011 01:26:20 -0500, Mark Pemberton
<mpe...@gm...> wrote:
> Welcome aboard Brett.
> 
> On Fri, Jan 28, 2011 at 12:24 AM, Christian Weiske  wrote:
>  Hi Brett,
> 
>  > I am new to open-source work and am currently familiarizing myself
>  > with git and the product code. I think this will be primarily a
>  > learning experience for me for a few weeks at least.
> 
>  That's totally fine. There is no need to rush, and we have plenty of
>  small tasks you can do to get into the code. If you need help, just
>  send a mail to the mailing list or join me/us in #semanticscuttle on
>  freenode. If you have jabber/xmpp, you might add cw...@cw...
> [2] to
>  your contact list.
> 
>  Btw, the mailing list is on
> 
> https://sourceforge.net/mailarchive/forum.php?forum_name=semanticscuttle-devel
> [3]
> 
>  You should at first get familiar with SemanticScuttle itself -
> download
>  it, install it and get it to work on your own machine.
> 
>  Since you are very new, you might implement a small feature request:
>  > "Make default privacy configurable"
> 
> http://sourceforge.net/tracker/?func=detail&aid=3164348&group_id=211356&atid=1017433
> [4]
> 
>  The steps to take are:
>  1. Find out what the things are needed to do to implement the
> feature
>  2. Look at the code and see what needs to be done where to do it
>  3. Write that up and send it to the mailing list. We can discuss it
> then
>  4. Create your own feature branch (i.e. "configurable-privacy") from
>    master and implement it in there
>  5. Push the branch to sourceforge so I can review it.
>  6. If everything is fine, I will merge it into the master branch
> 
>  If you find out that that's not your thing, you could help at
>  other places, i.e. the documentation.
> 
>  --
>  Regards/Mit freundlichen Grüßen
>  Christian Weiske
> 
>  -=≡ Geeking around in the name of science since 1982 ≡=-
> 
> ------------------------------------------------------------------------------
>  Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
>  Finally, a world-class log management solution at an even better
> price-free!
>  Download using promo code Free_Logger_4_Dev2Dev. Offer expires
>  February 28th, so secure your free ArcSight Logger TODAY!
>  http://p.sf.net/sfu/arcsight-sfd2d [5]
> _______________________________________________
>  Semanticscuttle-devel mailing list
>  Sem...@li... [6]
>  https://lists.sourceforge.net/lists/listinfo/semanticscuttle-devel
> [7]
> 
> 
> 
> Links:
> ------
> [1] mailto:cw...@cw...
> [2] mailto:cw...@cw...
> [3]
> https://sourceforge.net/mailarchive/forum.php?forum_name=semanticscuttle-devel
> [4]
> http://sourceforge.net/tracker/?func=detail&aid=3164348&group_id=211356&atid=1017433
> [5] http://p.sf.net/sfu/arcsight-sfd2d
> [6] mailto:Sem...@li...
> [7]
> https://lists.sourceforge.net/lists/listinfo/semanticscuttle-devel

Re: [Semanticscuttle-devel] Fix bugs, implement feature requests

[Brett D. <bs...@fr...>]

That sounds like a good place to start. I'm getting SemanticScuttle up
and running now.

Thanks.

Rgrds,
Brett


On Fri, 28 Jan 2011 06:24:20 +0100, Christian Weiske
<cw...@cw...> wrote:
> Hi Brett,
> 
> 
>> I am new to open-source work and am currently familiarizing myself
>> with git and the product code. I think this will be primarily a
>> learning experience for me for a few weeks at least.
> 
> That's totally fine. There is no need to rush, and we have plenty of
> small tasks you can do to get into the code. If you need help, just
> send a mail to the mailing list or join me/us in #semanticscuttle on
> freenode. If you have jabber/xmpp, you might add cw...@cw... to
> your contact list.
> 
> Btw, the mailing list is on 
> https://sourceforge.net/mailarchive/forum.php?forum_name=semanticscuttle-devel
> 
> You should at first get familiar with SemanticScuttle itself - download
> it, install it and get it to work on your own machine.
> 
> Since you are very new, you might implement a small feature request:
>> "Make default privacy configurable"
> http://sourceforge.net/tracker/?func=detail&aid=3164348&group_id=211356&atid=1017433
> 
> The steps to take are:
> 1. Find out what the things are needed to do to implement the feature
> 2. Look at the code and see what needs to be done where to do it
> 3. Write that up and send it to the mailing list. We can discuss it then
> 4. Create your own feature branch (i.e. "configurable-privacy") from
>    master and implement it in there
> 5. Push the branch to sourceforge so I can review it.
> 6. If everything is fine, I will merge it into the master branch
> 
> If you find out that that's not your thing, you could help at
> other places, i.e. the documentation.

Re: [Semanticscuttle-devel] Updates to privatekey branch (aka Private Rss Feed)

[Christian W. <cw...@cw...>]

Hi Mark,



> Hey guys, I've pushed the latest changes to the privatekey branch that
> contains two things.
> 
> First, I did some code cleanup which helped me get more familiar with
> the code base.
> 
> Second, I'm mostly done with the private RSS feed changes as per
> feature request # *3164013*.
> 
> What's still pending:
> 1) make either an update utility or change the tables.sql to include
> some code that auto populates the new user column with a unique md5()
> value.
The update utility is something I'd like to see ([1], [2]), but it's
not as easy as one might think :)
For now, please add the upgrade SQL statements to doc/UPGRADE.txt
and make sure that people without a private key in the database cannot
use the private bookmark feature.

> 2) I've only changed the bookmarks.php page to show the
> additional RSS feed. Before I propagate that change to the other
> pages with rss feeds, I'd like to specifically ask for thoughts on
> distinguishing the difference between the feeds.  Is the hover-text
> enough, or do we need to have a different icon for the private feed
> (like the common blue one).
I'd actually remove the feed icon from the pager and only keep the
icons in the HTML head (<link rel="alternate"/>).

Did you run the unittests yet? I think you have to adjust them and add
tests for your new functionality. Beware that running them will empty
the database, so back it up first.



[1] http://cweiske.de/tagebuch/php-installer-first.htm
[2]
http://cweiske.de/tagebuch/Generic%20PHP%20application%20installers.htm

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-= Geeking around in the name of science since 1982 =-

[Semanticscuttle-devel] Updates to privatekey branch (aka Private Rss Feed)

[Mark P. <mpe...@gm...>]

Hey guys, I've pushed the latest changes to the privatekey branch that
contains two things.

First, I did some code cleanup which helped me get more familiar with the
code base.

Second, I'm mostly done with the private RSS feed changes as per feature
request # *3164013*.

What's still pending:
1) make either an update utility or change the tables.sql to include some
code that auto populates the new user column with a unique md5() value.
2) I've only changed the bookmarks.php page to show the addiitonal RSS feed.
 Before I propagate that change to the other pages with rss feeds, I'd like
to specifically ask for thoughts on distinguishing the difference between
the feeds.  Is the hover-text enough, or do we need to have a different icon
for the private feed (like the common blue one).

I don't think there is anything else pending, but am certainly open to any
changes.

Thanks all,
Mark Pemberton

Re: [Semanticscuttle-devel] Fix bugs, implement feature requests

[Mark P. <mpe...@gm...>]

Welcome aboard Brett.


On Fri, Jan 28, 2011 at 12:24 AM, Christian Weiske <cw...@cw...>wrote:

> Hi Brett,
>
>
> > I am new to open-source work and am currently familiarizing myself
> > with git and the product code. I think this will be primarily a
> > learning experience for me for a few weeks at least.
>
> That's totally fine. There is no need to rush, and we have plenty of
> small tasks you can do to get into the code. If you need help, just
> send a mail to the mailing list or join me/us in #semanticscuttle on
> freenode. If you have jabber/xmpp, you might add cw...@cw... to
> your contact list.
>
> Btw, the mailing list is on
>
> https://sourceforge.net/mailarchive/forum.php?forum_name=semanticscuttle-devel
>
> You should at first get familiar with SemanticScuttle itself - download
> it, install it and get it to work on your own machine.
>
> Since you are very new, you might implement a small feature request:
> > "Make default privacy configurable"
>
> http://sourceforge.net/tracker/?func=detail&aid=3164348&group_id=211356&atid=1017433
>
> The steps to take are:
> 1. Find out what the things are needed to do to implement the feature
> 2. Look at the code and see what needs to be done where to do it
> 3. Write that up and send it to the mailing list. We can discuss it then
> 4. Create your own feature branch (i.e. "configurable-privacy") from
>   master and implement it in there
> 5. Push the branch to sourceforge so I can review it.
> 6. If everything is fine, I will merge it into the master branch
>
> If you find out that that's not your thing, you could help at
> other places, i.e. the documentation.
>
> --
> Regards/Mit freundlichen Grüßen
> Christian Weiske
>
> -=≡ Geeking around in the name of science since 1982 ≡=-
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Semanticscuttle-devel mailing list
> Sem...@li...
> https://lists.sourceforge.net/lists/listinfo/semanticscuttle-devel
>
>

Re: [Semanticscuttle-devel] Fix bugs, implement feature requests

[Christian W. <cw...@cw...>]

Hi Brett,


> I am new to open-source work and am currently familiarizing myself 
> with git and the product code. I think this will be primarily a 
> learning experience for me for a few weeks at least.

That's totally fine. There is no need to rush, and we have plenty of
small tasks you can do to get into the code. If you need help, just
send a mail to the mailing list or join me/us in #semanticscuttle on
freenode. If you have jabber/xmpp, you might add cw...@cw... to
your contact list.

Btw, the mailing list is on 
https://sourceforge.net/mailarchive/forum.php?forum_name=semanticscuttle-devel

You should at first get familiar with SemanticScuttle itself - download
it, install it and get it to work on your own machine.

Since you are very new, you might implement a small feature request:
> "Make default privacy configurable"
http://sourceforge.net/tracker/?func=detail&aid=3164348&group_id=211356&atid=1017433

The steps to take are:
1. Find out what the things are needed to do to implement the feature
2. Look at the code and see what needs to be done where to do it
3. Write that up and send it to the mailing list. We can discuss it then
4. Create your own feature branch (i.e. "configurable-privacy") from
   master and implement it in there
5. Push the branch to sourceforge so I can review it.
6. If everything is fine, I will merge it into the master branch

If you find out that that's not your thing, you could help at
other places, i.e. the documentation.

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-

[Semanticscuttle-devel] Message to Brett / bretticvs

[Christian W. <cw...@cw...>]

Hi Brett,


I hope you read that list, because I always get a 
> <bre...@us...>:
>  host mx.sourceforge.net[216.34.181.68] said:
> 550 unknown user (in reply to RCPT TO command)

Please contact me from your regular email account.


-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-

Re: [Semanticscuttle-devel] SQL Calls

[Christian W. <cw...@cw...>]

Hi Mark,


> > What's the state of the private feed link? I'd like to see this
> > finished first.
> Agreed, hope to have this done shortly.  Got into cleaning up code
> which helped me get more familiar with the code.  My desire is to
> have it completely tested by the weekend (depending on my schedule).
No need to rush, it's a spare time project :)


> > Regarding the SQL calls: I don't like AdoDB that is used in
> > semantiscuttle currently, and would rather switch to PEAR's MDB2 or
> > plain PDO. MDB2 does real abstraction but is PHP4 (thus not E_STRICT
> > compatible), whereas PDO does not really do any abstraction but is
> > available in PHP itself and fast.
> > Do you have any preferences?
> This is a tough call because it depends on where our focus is.  We can
> certainly go with PDO which is a great standard and has little
> overhead. The downside is that to support multiple databases would
> require altering the SQL commands based on the database type.  An
> alternative is something like Active Record (Propel, Doctrine, etc)
> where everything is contained in the class.  The downside to AR is
> that it has a huge overhead and requires bytecode cache to maximize
> performance.  So the question is, what is our focus: do we focus on
> having less overhead with PDO and refining what db's we support or go
> with Active Record?  I personally think that AR may have too much
> overhead than what we really need (but would be really cool).

I would also prefer PDO since it's fast and doesn't have much overhead.
An ORM is too large for us IMO. So let's go with PDO.


-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-= Geeking around in the name of science since 1982 =-

Re: [Semanticscuttle-devel] SQL Calls

[Christian W. <cw...@cw...>]

Hi Mark,


> I've read a couple people state they've had performance issues with
> larger installs and that you've prototyped some updates to the SQL
> calls to possibly fix the issue.  One of my strengths is db calls and
> would love to take that if you like.  I've got tons of Oracle
> experience and have noticed that some of the SQL calls aren't Oracle
> friendly (i.e. LIMIT, LIKE, etc). Granted I don't think most of our
> user base will be using Oracle, but would LOVE to taunt that as an
> option.  :)

What's the state of the private feed link? I'd like to see this
finished first.

Regarding the SQL calls: I don't like AdoDB that is used in
semantiscuttle currently, and would rather switch to PEAR's MDB2 or
plain PDO. MDB2 does real abstraction but is PHP4 (thus not E_STRICT
compatible), whereas PDO does not really do any abstraction but is
available in PHP itself and fast.
Do you have any preferences?

When I tried to fix the issue with the huge number of bookmarks, I had
to dive really deep in SQL generation. Fixing the DB layer first would
be better in my eyes, because it would perhaps ease the later
optimization.


> My db doesn't have 30k of links, but I can easily dump
> an ton of dummy links in there.
There is a dummy-bookmark generation script in scripts/, maybe it helps.

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-= Geeking around in the name of science since 1982 =-

Re: [Semanticscuttle-devel] privatekey implementation (Was: Git on sourceforge filled / release task for Eric)

[Christian W. <cw...@cw...>]

Hi Mark,


> Thanks for the reply Christian.  Question about something you added
> to the Feature Request about giving them partial access if
> authenticated via the private key.  My thought is to give them full
> access but put some code in the authentication method with maxtries
> or something to thwart hacks.  I could go either way on this, so let
> me know what you think.
The user is either allowed to use the api or not - I would
not differentiate between "partially authenticated" and normal users.
That would lead to code that is hard to read and hard to understand.

I thought that partial access would suffice here because the key is
currently only needed for the feed. It should not be used with the API,
because the api should be used as it exists now (with http
authentication over a secure line).

The private feed will often be used without ssl (because people often
do not know how to set that up), and can easily be sniffed or get lost.
That's why we need an easy way to change it.

So for starters, allow the key on the feed only. If that works well and
people just want to have it elsewhere, we can always implement that.

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-

Re: [Semanticscuttle-devel] Git on sourceforge filled / release task for Eric

[Mark P. <mpe...@gm...>]

Thanks for the reply Christian.  Question about something you added to the
Feature Request about giving them partial access if authenticated via the
private key.  My thought is to give them full access but put some code in
the authentication method with maxtries or something to thwart hacks.  I
could go either way on this, so let me know what you think.


On Sat, Jan 22, 2011 at 5:02 PM, Christian Weiske <cw...@cw...>wrote:

> Hi Mark,
>
>
> > 1) alter user table to include "privateKey" as varchar(32) with
> > unique index
> Yep.
>
> > 2) alter user db model to include new column
> I don't know if it's necessary; the user model is not used much yet
> IIRC.
>
> > 3) alter user service, specifically function getCurrentUserId() to
> > include looking at URL for &privatekey=
>
> > 4) alter api/* scripts to include privatekey auth
> Changing www/api/httpauth.inc.php should suffice, and the rss.php file.
> Maybe it should also just use the httpauth.inc.php file, but not
> require authentication (unlike the api files do); only use it to get
> login data if they are passed.
>
> > 5) alter template/profile.php and template/user.php to allow user to
> > see and possibly alter the 32 length key.  Validation is definitely
> > required (len=32 and unique)
> I would not let the user manually enter a new key. Regenerating it is a
> better alternative. md5() returns 32 char strings. If you combine
> time() + rand() + a salt, you'll get pretty unique keys :)
>
> > 6) create upgrade script to fill new column with values
> perhaps you can get mysql to do that automatically and just add the
> SQL command to doc/upgrade.txt
>
> > I'm assuming it'll need to be alpha(upper and lower)+numeric value?
> md5 only returns numbers + lowercase letters, so this suffices.
>
>
>
> PS: Please send the mail to the list only, so everyone can participate
> and I don't get doubles :)
>
> --
> Regards/Mit freundlichen Grüßen
> Christian Weiske
>
> -=≡ Geeking around in the name of science since 1982 ≡=-
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Semanticscuttle-devel mailing list
> Sem...@li...
> https://lists.sourceforge.net/lists/listinfo/semanticscuttle-devel
>
>

Re: [Semanticscuttle-devel] Git on sourceforge filled / release task for Eric

[Christian W. <cw...@cw...>]

Hi Mark,


> 1) alter user table to include "privateKey" as varchar(32) with
> unique index
Yep.

> 2) alter user db model to include new column
I don't know if it's necessary; the user model is not used much yet
IIRC.

> 3) alter user service, specifically function getCurrentUserId() to
> include looking at URL for &privatekey=

> 4) alter api/* scripts to include privatekey auth
Changing www/api/httpauth.inc.php should suffice, and the rss.php file.
Maybe it should also just use the httpauth.inc.php file, but not
require authentication (unlike the api files do); only use it to get
login data if they are passed.

> 5) alter template/profile.php and template/user.php to allow user to
> see and possibly alter the 32 length key.  Validation is definitely
> required (len=32 and unique)
I would not let the user manually enter a new key. Regenerating it is a
better alternative. md5() returns 32 char strings. If you combine
time() + rand() + a salt, you'll get pretty unique keys :)

> 6) create upgrade script to fill new column with values
perhaps you can get mysql to do that automatically and just add the
SQL command to doc/upgrade.txt

> I'm assuming it'll need to be alpha(upper and lower)+numeric value?
md5 only returns numbers + lowercase letters, so this suffices.



PS: Please send the mail to the list only, so everyone can participate
and I don't get doubles :)

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-

Re: [Semanticscuttle-devel] Git on sourceforge filled / release task for Eric

[Christian W. <cw...@cw...>]

Hi Mark,



> I would love to work on the private key feature if you would like.
That's a good idea; it's a small task that still lets you work on
several parts of SemanticScuttle.
If you like you could write an email sketching out how you
would solve the problem, and we can discuss the issue. If not, just get
on hacking :)


> I'm not going to lie and tell you I know everything about source
> control management but I'm familiar with the basic workings of SVN.
> Working on getting up to speed with GIT.  With that said, my guess is
> that I make a clone of the master branch to make my changes and then
> that will be merged when it is complete?
Yes, that's about it:
1. Create a new branch from the master branch and use that (checkout)
2. Do your changes, commit them to your branch
3. Push the changes in your branch regularly to the semantiscuttle git
   repository. You all should have write access. 
4. When you're done, tell me. I will review your changes, say what
   could be better and finally merge it into the master branch.
5. Please do not commit to the master branch yourself.

If anyone of you have questions, I'm regularly online in irc
(semantiscuttle on freenode) and in jabber - don't hesitate to ask.

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-

Re: [Semanticscuttle-devel] Git on sourceforge filled / release task for Eric

[Mark P. <mpe...@gm...>]

I would love to work on the private key feature if you would like.  I'm not
going to lie and tell you I know everything about source control management
but I'm familiar with the basic workings of SVN.  Working on getting up to
speed with GIT.  With that said, my guess is that I make a clone of the
master branch to make my changes and then that will be merged when it is
complete?  I'm open to however you want me to do it.

Thanks,
Mark

On Sat, Jan 22, 2011 at 12:49 PM, Christian Weiske <cw...@cw...>wrote:

> Hi again,
>
>
> > @Eric:
> > It seems that I did not tag the releases in git, only in svn. Could
> > you please find out which of the git commits was the latest before
> > releasing 0.97.0 (look in svn)?
> > Please create a "0.97" branch starting from that commit and merge the
> > important bug fixes (crashes) that have been fixed in the meantime
> > into it.
> > The question now is: Which bugfixes are the important ones?
> > I remember two crashes and the javascript problem on the bookmarklet
> > page. The changelog contains a list of unreleased changes, so finding
> > them should be possible.
>
> I just assigned you a task and don't even know how familiar you are
> with svn, git and php release management (phing) in general.
> So what do you say? Maybe implementing a feature from the bug tracker
> would be a better first task for you?
>
> --
> Regards/Mit freundlichen Grüßen
> Christian Weiske
>
> -=≡ Geeking around in the name of science since 1982 ≡=-
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Semanticscuttle-devel mailing list
> Sem...@li...
> https://lists.sourceforge.net/lists/listinfo/semanticscuttle-devel
>
>

Re: [Semanticscuttle-devel] Git on sourceforge filled / release task for Eric

[Christian W. <cw...@cw...>]

Hi again,


> @Eric:
> It seems that I did not tag the releases in git, only in svn. Could
> you please find out which of the git commits was the latest before
> releasing 0.97.0 (look in svn)?
> Please create a "0.97" branch starting from that commit and merge the
> important bug fixes (crashes) that have been fixed in the meantime
> into it.
> The question now is: Which bugfixes are the important ones?
> I remember two crashes and the javascript problem on the bookmarklet
> page. The changelog contains a list of unreleased changes, so finding
> them should be possible.

I just assigned you a task and don't even know how familiar you are
with svn, git and php release management (phing) in general.
So what do you say? Maybe implementing a feature from the bug tracker
would be a better first task for you?

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-

[Semanticscuttle-devel] Git on sourceforge filled / release task for Eric

[Christian W. <cw...@cw...>]

Hi all,


I created an "sc" repository on the sourceforge git server and pushed
my local repository onto it, creating three branches:
- master
- jquery
- quickform

The repositories are available anonymously on
> git://semanticscuttle.git.sourceforge.net/gitroot/semanticscuttle/sc
and read-writable on
> ssh://USER@semanticscuttle.git.sourceforge.net/gitroot/semanticscuttle/sc
(replace USER with your SourceForge user name)

To get a clone of it just do a 
$ git clone $url
and you're set.


@Eric:
It seems that I did not tag the releases in git, only in svn. Could you
please find out which of the git commits was the latest before
releasing 0.97.0 (look in svn)?
Please create a "0.97" branch starting from that commit and merge the
important bug fixes (crashes) that have been fixed in the meantime
into it.
The question now is: Which bugfixes are the important ones?
I remember two crashes and the javascript problem on the bookmarklet
page. The changelog contains a list of unreleased changes, so finding
them should be possible.


-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-

Re: [Semanticscuttle-devel] regarding "help wanted" post

[Eric C <eco...@el...>]

Which branch in your git-hub account should be used for forking? I see 4...

quickform, jquery, master, pearpkg

Also, the last update I see is October 9th, am I looking at the right branches?
https://github.com/cweiske/SemanticScuttle/branches

Thanks,

 -Eric

Re: [Semanticscuttle-devel] regarding "help wanted" post

[Christian W. <cw...@cw...>]

Hello Golanor,


> I would like to offer my help with your project.
> i have some PHP knowledge, little MySQL knowledge, and a lot
> of free time.
> let me know if you still need help.
Yes, we still need help, and you are very welcome.
Please subscribe to the semantiscuttle-devel mailing list and look in
the archive; I posted a status mail this morning - this should help you
getting an overview.

@all: Benjamin told me that he will resign. Thanks for all your work!
Now that Benjamin is gone, I'll officially switch from subversion to
git and create a repository on sourceforge.
Until that is done, please fork my github repository and work on that.


Golanor, it'd be cool if you could try out SemanticScuttle by
installing it on your local machine, run the unit tests, play around
with it to get familiar with the code base.
A task that you could do is prepare the release 0.97.2 as I described
in my status mail ("Next tasks for SemanticScuttle").

If you need help, don't hesitate to write on the dev list or join me on
the semanticscuttle IRC channel on freenode
(http://semanticscuttle.sourceforge.net/)

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-= Geeking around in the name of science since 1982 =-

Re: [Semanticscuttle-devel] Next tasks for SemanticScuttle

[Benjamin Huynh-Kim-B. <men...@gm...>]

Hi,
just a quick remark.
I think you are totally able to lead this project from A to Z.
If you want to put it from SVN to Git, do not hesitate any more. I do not
think I will have time to come back on this project in the future.
SemanticScuttle is now all into your hands.

It was a great pleasure to see a skillful person such as you arriving on
this project.

Good luck and good bye.


Benjamin HUYNH-KIM-BANG
http://benjamin.hkb.fr


On Wed, Jan 19, 2011 at 9:53 PM, Christian Weiske <cw...@cw...>wrote:

> Hi all,
>
>
> I especially welcome Mark Pemberton who volunteered to support us
> improving SemanticScuttle by hacking on the code.
>
>
> Current status
> --------------
> Until September 2009, Benjamin Huynh-Kim-Bang mostly worked on SC and
> Eric Dane committed some patches.
> Sept 2009 is the time I started hacking on SC, and released 7 new
> versions in the meantime.
>
> The new versions were feature releases as well as security and bugfix
> releases. Our latest version, 0.97.1, is mostly stable and partly
> unit-tested code. Unfortunately, there are some serious bugs in it (PHP
> parse errors/fatal errors) - all of them have been fixed in my
> repository on github.
>
> I have also been working on several major changes that are not finished
> yet and live in their own branch:
> - jQuery: replace the dojo javascript library with jQuery.
> - QuickForm: Use PEAR's HTML_QuickForm2 for all forms.
>
> The jquery port ist 90% done, we only miss a library for autocompletion
> of tags in the bookmark form. I originally tried to use the FCBKeditor
> component and hacked several months on it, but I believe we should
> start fresh or get a better one.
> It gives us the ability to host the js libs on our own server and
> finally get rid of all the javascript warnings we currently get.
>
> The quickform integration would give us the ability to easily secure our
> form with i.e. captchas, give us better validation, less code and
> better error handling.
> I already converated the registriation, login and password forgotten
> form to use quickform. Still quite a lot to do here, but I think
> it's worth it.
>
> So far about the work that's currently in progress.
>
> Getting a new version 0.97.2 with all the serious bugs fixed out should
> be the next task.
>
>
> The future
> ----------
> There are other things that I'd really like to see in SemanticScuttle
> soon:
> - Theming capability. Just extract a theme folder in data/templates/
>  and you're done. This is relatively easy work since the task is to
>  add another folder level below data/templates/, the theme folder name,
>  and implement fallbacks to the default template if the theme does not
>  ship with the requested file
> - OpenID integration. There is a feature request for it, but no work
>  has been done yet. I'd use the PEAR OpenId library for it and extend
>  the user table with an openid column. Should not be that hard :)
> - pubsubhubbub integration to propagate new bookmarks between separate
>  SC instances automatically. Imagine your friend does also have a SC
>  instance, and you simply subscribe to his bookmarks. As soon as he
>  adds a new bookmark, his SC instance notifies the hub which in turn
>  notifies your own subscribed SC instance. Your SC imports the
>  bookmark and marks it as "owned by $friend". Benefits:
>  1. search in your local SC and get find your friend's bookmarks
>  2. data get distributed so that they don't get lost easily (backup)
> - Make installation easier. I wrote some blog posts about that and hope
>  that the arbit installer gets usable soonish.
>
> Apart from that, we need a demo instance on
> http://semanticscuttle.sourceforge.net since the .fr address is down.
> Proper documentation would also be awesome, and we should decide if we
> use the trac instance or the "normal" sourceforge tracker.
>
>
> Technical details
> -----------------
> The code is hosted in a SVN repository on sourceforge[0], but I
> personally keep my branches on github[1] because I can commit offline
> in git.
> We have unit tests (based on phpunit) that cover a growing part of the
> code. Unfortunately not everything is covered - we would not have so
> many bugs - but we're on a good track.
>
>
> So much for now.
>
>
> [0] http://sourceforge.net/scm/?type=svn&group_id=211356
> [1] https://github.com/cweiske/SemanticScuttle
>
> --
> Regards/Mit freundlichen Grüßen
> Christian Weiske
>
> -=≡ Geeking around in the name of science since 1982 ≡=-
>
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Semanticscuttle-devel mailing list
> Sem...@li...
> https://lists.sourceforge.net/lists/listinfo/semanticscuttle-devel
>
>

[Semanticscuttle-devel] Next tasks for SemanticScuttle

[Christian W. <cw...@cw...>]

Hi all,


I especially welcome Mark Pemberton who volunteered to support us
improving SemanticScuttle by hacking on the code.


Current status
--------------
Until September 2009, Benjamin Huynh-Kim-Bang mostly worked on SC and
Eric Dane committed some patches.
Sept 2009 is the time I started hacking on SC, and released 7 new
versions in the meantime.

The new versions were feature releases as well as security and bugfix
releases. Our latest version, 0.97.1, is mostly stable and partly
unit-tested code. Unfortunately, there are some serious bugs in it (PHP
parse errors/fatal errors) - all of them have been fixed in my
repository on github.

I have also been working on several major changes that are not finished
yet and live in their own branch:
- jQuery: replace the dojo javascript library with jQuery.
- QuickForm: Use PEAR's HTML_QuickForm2 for all forms.

The jquery port ist 90% done, we only miss a library for autocompletion
of tags in the bookmark form. I originally tried to use the FCBKeditor
component and hacked several months on it, but I believe we should
start fresh or get a better one.
It gives us the ability to host the js libs on our own server and
finally get rid of all the javascript warnings we currently get.

The quickform integration would give us the ability to easily secure our
form with i.e. captchas, give us better validation, less code and
better error handling.
I already converated the registriation, login and password forgotten
form to use quickform. Still quite a lot to do here, but I think
it's worth it.

So far about the work that's currently in progress.

Getting a new version 0.97.2 with all the serious bugs fixed out should
be the next task.


The future
----------
There are other things that I'd really like to see in SemanticScuttle
soon:
- Theming capability. Just extract a theme folder in data/templates/
  and you're done. This is relatively easy work since the task is to
  add another folder level below data/templates/, the theme folder name,
  and implement fallbacks to the default template if the theme does not
  ship with the requested file
- OpenID integration. There is a feature request for it, but no work
  has been done yet. I'd use the PEAR OpenId library for it and extend
  the user table with an openid column. Should not be that hard :)
- pubsubhubbub integration to propagate new bookmarks between separate
  SC instances automatically. Imagine your friend does also have a SC
  instance, and you simply subscribe to his bookmarks. As soon as he
  adds a new bookmark, his SC instance notifies the hub which in turn
  notifies your own subscribed SC instance. Your SC imports the
  bookmark and marks it as "owned by $friend". Benefits:
  1. search in your local SC and get find your friend's bookmarks
  2. data get distributed so that they don't get lost easily (backup)
- Make installation easier. I wrote some blog posts about that and hope
  that the arbit installer gets usable soonish.

Apart from that, we need a demo instance on
http://semanticscuttle.sourceforge.net since the .fr address is down.
Proper documentation would also be awesome, and we should decide if we
use the trac instance or the "normal" sourceforge tracker.


Technical details
-----------------
The code is hosted in a SVN repository on sourceforge[0], but I
personally keep my branches on github[1] because I can commit offline
in git.
We have unit tests (based on phpunit) that cover a growing part of the
code. Unfortunately not everything is covered - we would not have so
many bugs - but we're on a good track.


So much for now.


[0] http://sourceforge.net/scm/?type=svn&group_id=211356
[1] https://github.com/cweiske/SemanticScuttle

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-

[Semanticscuttle-devel] Security release: SemanticScuttle 0.97.1 is out

[Christian W. <cw...@cw...>]

Hello fellow bookmarkers,


Some minutes ago, I released SemanticScuttle version 0.97.1 which fixes
a critical security issue related to deleting posts via the
delicious-compatible API.

Please update your installations as soon as possible, since a malicious
attacker might empty your database.

Downloads are available at:
http://sourceforge.net/projects/semanticscuttle/files/


-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-

Re: [Semanticscuttle-devel] SemanticScuttle js problem

[Christian W. <cw...@cw...>]

Hello Jakub,Am Wed, 22 Sep 2010 16:35:37 +0200




> After install clear SemanticScuttle installation tags.php page return
> many js errors.
> For example page like /www/tags.php/test load without any problems.
> After about 10 sec firebug on FF starts display error "uncaught
> exception: Could not load cross-domain resources: "
> This error is display in loop. Each one after about 0.5 sec.
I see that problem. Would you be so nice and open a bug report?


> PS.
> I apply to be part of Your developers tema but I was not accepted for
> now. I did some small bug fix in main code of SemanticScuttle project
> so maybe it will be good if I send commit to Your svn repository.
Please either open a bug report and attach the patch, or send the patch
directly to me or the developers list. I will review the patch then and
commit it if it's ok. After some good patches, I'll probably give you
commit karma.

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-

Re: [Semanticscuttle-devel] performance problem with mysql query

[Eric C <eco...@el...>]

Christian,

Thanks for the response.  I've updated the info on stack overflow, but
there is still a problem...

The query is well optimized, but it does not return the same results
as the original query.

For example I have 3 entries in table "sc_bookmarks".

bId           bModified      bHash
------------------------------------
2000-11-10    aaaaaa         ...
2011-12-12    bbbbbb         ...
2010-11-11    aaaaaa         ...
The query should return only row id 1 and 2. But it return all 3
records. Seems mysql doesn't like: ´GROUP BY B.bModified DESC, B.bHash
DESC´

I tried to change ´GROUP BY B.bModified DESC, B.bHash DESC´

to ´GROUP BY B.bModified, B.bHash GROUP BY B.bHash, B.bModified´

but I'm still getting all 3 records.

It works when I leave ´GROUP BY B.bHash´ but that prevents the index
from working.

http://stackoverflow.com/questions/3722253/help-removing-mysql-file-sort

Thanks,

 -Eric

On Sat, Sep 18, 2010 at 8:44 PM, Christian Weiske <cw...@cw...> wrote:
> Hello Eric,
>
>
>> Mysql is using a file sort on one of the queries used to generate the
>> homepage.... This is taking about 4 seconds of 100% cpu on my box...
>>
>> I'm trying to optimize it, but don't have the required experience.
>>
>> Here are the details:
>> http://stackoverflow.com/questions/3722253/help-removing-mysql-file-sort
>
> The query needs to be as follows:
>
> SELECT U.username, B.*
>  FROM sc_users AS U, sc_bookmarks AS B
>  WHERE B.uId = U.uId AND B.bStatus = 0
>  GROUP BY B.bModified DESC, B.bHash DESC
>  ORDER BY B.bModified DESC
> LIMIT 10
>
> and you should create an index on status+modified+hash.
>
> --
> Regards/Mit freundlichen Grüßen
> Christian Weiske
>
> -=≡ Geeking around in the name of science since 1982 ≡=-
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Semanticscuttle-devel mailing list
> Sem...@li...
> https://lists.sourceforge.net/lists/listinfo/semanticscuttle-devel
>
>

Re: [Semanticscuttle-devel] performance problem with mysql query

[Christian W. <cw...@cw...>]

Hello Eric,


> Mysql is using a file sort on one of the queries used to generate the
> homepage.... This is taking about 4 seconds of 100% cpu on my box...
> 
> I'm trying to optimize it, but don't have the required experience.
> 
> Here are the details:
> http://stackoverflow.com/questions/3722253/help-removing-mysql-file-sort

The query needs to be as follows:

SELECT U.username, B.*
 FROM sc_users AS U, sc_bookmarks AS B
 WHERE B.uId = U.uId AND B.bStatus = 0
 GROUP BY B.bModified DESC, B.bHash DESC
 ORDER BY B.bModified DESC
LIMIT 10

and you should create an index on status+modified+hash.

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-