Re: Project jcal author passed away in 2017

[Ineiev]

On Sun, Dec 24, 2023 at 01:55:32PM +0330, masoud naservand wrote:
> I saw that https://www.nongnu.org/jcal/ is still mentioning
> Mr.Ghassemi as the maintainer. It is with sadness that I have to inform you
> that he passed away in 2017. See https://jadi.net/2017/10/ashkan-ghasemi/
> The linux community of Iran seems to have chosen
> https://github.com/persiancal/jcal as the replacement fork of this project.
> I'm wondering if it is possible for the savannah page to link to this fork.

Github is hostile to free software.  Being volunteers for the GNU
project, Savannah admins can't recommend it.


signature.asc
Description: PGP signature

[sr #110988] (wishlist) more php warnings

[Ineiev]

Follow-up Comment #8, sr#110988 (group administration):

[comment #7 comment #7:]
> another one:
> 
> AH01071: Got error 'PHP message:
/usr/local/share/savane/frontend/php/include/account.php:188:
...
> PHP message:
/usr/local/share/savane/frontend/php/include/account.php:193:...

Thank you, fixed.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #109703] package savane for debian

[Jing Luo]

Follow-up Comment #7, sr#109703 (group administration):

Fine. Just forget about what I said. Savane doesn't depend on those. Savannah
uses some of them.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110988] (wishlist) more php warnings

[Ineiev]

Follow-up Comment #9, sr#110988 (group administration):

[comment #6 comment #6:]
> [Tue Dec 26 20:42:47.401643 2023] [proxy_fcgi:error] [pid 67929:tid
140014675506880] [remote 240b::] AH01071: Got error 'PHP message:
/usr/local/share/savane/frontend/php/include/sane.php:421: [E_WARNING]
foreach() argument must be of type array|object, string given
...
> And then a big one spamming error.log, referer: project/admin/useradmin.php,
trimming a part of the message:

I can't reproduce these.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110988] (wishlist) more php warnings

[Jing Luo]

Follow-up Comment #10, sr#110988 (group administration):


[comment #9 comment #9:]
> [comment #6 comment #6:]
> > [Tue Dec 26 20:42:47.401643 2023] [proxy_fcgi:error] [pid 67929:tid
140014675506880] [remote 240b::] AH01071: Got error 'PHP message:
/usr/local/share/savane/frontend/php/include/sane.php:421: [E_WARNING]
foreach() argument must be of type array|object, string given
> ...

OK, this one is my fault. I played around with the code.

> > And then a big one spamming error.log, referer:
project/admin/useradmin.php, trimming a part of the message:
> 
> I can't reproduce these.

Did you use php 8.2? It seems to me that php is complaining about the null
value from the db "groups" table, but the backtrace is incomplete.

And here's a spooky one:

AH01071: Got error 'rms.php:666: [E_WARNING] Trying to access array offset on
value of type null\nbacktrace:\n{\n\n}

rms.php?


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110988] (wishlist) more php warnings

[Ineiev]

Follow-up Comment #11, sr#110988 (group administration):

[comment #10 comment #10:]
> AH01071: Got error 'rms.php:666: [E_WARNING] Trying to access array offset
on value of type null\nbacktrace:\n{\n\n}
> 
> rms.php?

userperms.php truncated, I guess.

Now I've found and fixed it; thanks.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110995] Private Git Repo

[Jason Self]

URL:
  

 Summary: Private Git Repo
   Group: Savannah Administration
   Submitter: jxself
   Submitted: Thu 28 Dec 2023 11:15:24 AM PST
Category: Additional Git repositories
Priority: 5 - Normal
Severity: 3 - Normal
  Status: None
 Assigned to: None
Originator Email: 
Operating System: None
 Open/Closed: Open
 Discussion Lock: Any


___

Follow-up Comments:


---
Date: Thu 28 Dec 2023 11:15:24 AM PST By: Jason Self 
I'd like to arrange, somehow, for a private git repository on the www project
used by gnu.org, named chief-webmaster-docs. Private in the sense that both
read and write access would be limited to specific members of the project.

The people with access should be myself and Dora. More may be added; I need to
consult with Dora.

>From the conversation on IRC today:

10:56 < rwp> Private git repos are trivially easy to set up.  No problem at
all.
10:57 < rwp> There is no web UI for setting them up.  They just need to be
created manually.  But that's trivially easy.
10:57 < jxself> Can access be limited to a sub-list of project members?
10:58 < rwp> There are two main sides of things.  The main git repos use Unix
group permissions using accounts stored in the SQL 
 database, maintained by the web UI.  And then there are accounts
not in the SQL database not maintained by the web UI.
10:59 < rwp> I am trying to recall how the cgitrc and gitweb files are
created.  I vaguely recall there being a filter that either 
 includes or excludes projects from the public listing.  But
regardless that would need to be reviewed and something 
 easy could be set up either way.







___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110995] Private Git Repo

[Bob Proulx]

Update of sr#110995 (group administration):

 Assigned to:None => rwp

___

Follow-up Comment #1:

What name would you like to call the git repository?



___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110995] Private Git Repo

[Bob Proulx]

Update of sr#110995 (group administration):

  Status:None => In Progress

___

Follow-up Comment #2:

Oh!  I missed the detail.  chief-webmaster-docs is perfect.  I will set this
up.



___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110995] Private Git Repo

[Bob Proulx]

Update of sr#110995 (group administration):

  Status: In Progress => Done   
 Open/Closed:Open => Closed 

___

Follow-up Comment #3:

Done.  Access to the www team members only.



___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110995] Private Git Repo

[Jason Self]

Update of sr#110995 (group administration):

 Open/Closed:  Closed => Open   

___

Follow-up Comment #4:

Actually, I'm looking for access to a subset of the www team members. To
quote:

"The people with access should be myself and Dora. More may be added; I need
to consult with Dora."

Is that doable?


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[sr #110995] Private Git Repo

[Ineiev]

Follow-up Comment #5, sr#110995 (group administration):

I suggest registering a new private group and adding people who need an access
to it.  Our software has no means to distinguish between private and public
repositories within a group, and I don't think we should support that.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/