Hi Folks,
I'm seddik, I have joined Fedora Infrastructure Community in July 2020 as a
contributor. So I'm helping with automation and monitoring tasks.
I have a little experience on python programming, and would be happy to get
involved as much as ever.
Please feel free to help me with any docume
Hello, does anybody want to take this? If not, I will.
Forwarded Message
Subject:Python SIG at Fedora Council Video Meeting
Date: Thu, 6 Jan 2022 16:06:17 -0500
From: Tom Callaway
To: Miro Hrončok
Miro, I know you're in the Python SIG, please forward
On 06. 05. 20 11:19, Felix Schwarz wrote:
https://bugzilla.redhat.com/buglist.cgi?bug_id=1797129&bug_id_type=anddependson&format=tvp&list_id=11041137#
(click "Expand all" for the full horror show
Or if you need another horror show, see:
https://bugzilla.redhat.com/showdependencytree.cgi?id=PYT
Hi Jens,
Am 05.05.20 um 21:28 schrieb Adrian Adrian:
> I was looking to join Fedora development, and as I'm most familiar with
> Python, I thought the Python SIG would be my way to go. Following the
> https://fedoraproject.org/wiki/SIGs/Python/JoinSIG guide, it suggests to
Hi guys, I was looking to join Fedora development, and as I'm most familiar with Python, I thought the Python SIG would be my way to go. Following the https://fedoraproject.org/wiki/SIGs/Python/JoinSIG guide, it suggests to post a self-introduction to the mailing list, so that's what I&#
A friendly reminder that the on-boarding issue [1] isn't resolved yet. Please
sponsor your sponsored members to *python-packagers-sig*.
If all the members have been sponsored, I can request for editing the groups
and switching pkgdb to use *python-packagers-sig* instead of python-sig.[2
> There is some serious discussion happening on the Infrastructure
> ticket[1] about establishing two FAS groups. pingou has suggested that we
> involve some
> more admins from the Python SIG group to arrive at a feasible solution. I
> request all
> senior persons to give thei
> CommOps is currently working on the Python SIG On-Boarding ticket [1] and one
> of the tasks
> we have identified is re-writing the Python SIG wiki page to make it more
> beginner-friendly. I was assigned with this particular task which is now
> complete [2] [3].
> We rece
> I was wondering whether it is a good time to make the new pages official.
> Also, I would
> like to know whether the idea of splitting the SIG into two FAS groups is
> acceptable so
> that we can start taking necessary actions.
As instructed by jflory7, I've opened up a ticket on the Fedora-I
+1 on everything
Charalampos Stratakis
Associate Software Engineer
Python Maintenance Team, Red Hat
- Original Message -
From: "Dhanesh Bhalchandra Sabane"
To: [email protected]
Sent: Tuesday, September 13, 2016 7:27:48 PM
Subject: Re: Python SIG on-boar
On Tue, Sep 13, 2016 at 10:36 AM, Miro Hrončok wrote:
> On 13.9.2016 19:27, Dhanesh Bhalchandra Sabane wrote:
>
>> Aloha Python-SIG!
>> I was wondering whether it is a good time to make the new pages official.
>> Also, I would like to know whether the idea of splitting
On 13.9.2016 19:27, Dhanesh Bhalchandra Sabane wrote:
Aloha Python-SIG!
I was wondering whether it is a good time to make the new pages official. Also,
I would like to know whether the idea of splitting the SIG into two FAS groups
is acceptable so that we can start taking necessary actions
Aloha Python-SIG!
I was wondering whether it is a good time to make the new pages official. Also,
I would like to know whether the idea of splitting the SIG into two FAS groups
is acceptable so that we can start taking necessary actions.
> CommOps is currently working on the Python SIG
+1
2016-09-06 13:42 GMT-05:00 Dhanesh Bhalchandra Sabane <
[email protected]>:
> CommOps is currently working on the Python SIG On-Boarding ticket [1] and
> one of the tasks we have identified is re-writing the Python SIG wiki page
> to make it more beginner-friendly.
On 7 September 2016 at 04:42, Dhanesh Bhalchandra Sabane
wrote:
> CommOps is currently working on the Python SIG On-Boarding ticket [1] and one
> of the tasks we have identified is re-writing the Python SIG wiki page to
> make it more beginner-friendly. I was assigned with this partic
andra Sabane"
To: [email protected]
Sent: Tuesday, September 6, 2016 8:42:37 PM
Subject: Python SIG on-boarding issue
CommOps is currently working on the Python SIG On-Boarding ticket [1] and one
of the tasks we have identified is re-writing the Python SIG wiki page to mak
CommOps is currently working on the Python SIG On-Boarding ticket [1] and one
of the tasks we have identified is re-writing the Python SIG wiki page to make
it more beginner-friendly. I was assigned with this particular task which is
now complete [2] [3]. We received some feedback from
On 15/08/16 16:06, Petr Viktorin wrote:
>
> Then there are always things others would like help with in their quest
> to make Fedora better. For example, in the Python 3 effort, there's a
> tracking bug for cases where the packager doesn't have time to do the
> Python3 port. Some of the bugs ther
/python-3.6
Please be aware that this is an alpha version and the copr builds so far are
experimental (some patches need reviewing, some package changes are not
documented etc), so builds might disappear, updated, downgraded etc.
As an added note, Python-SIG wiki page is (slowly) being updated [1
place to ask.
As for the inevitable fires, unless it's an embargoed security issues
there should be a public bug on Bugzilla, and usually a flurry of
activity on this list or IRC. See the recent majorver-provides
discussion for example.
I'm hoping to work with the members of py
;t know where to start helping effectively.
I'm hoping to work with the members of python-sig to learn the ropes and
join the team. I am not just curious, I am determined. Driven even. I would
like to take that energy and apply it to python-sig. I look forward to
getting to know you all and
Please realize that I first clicked on the python-sig request in FAS nearly
a year ago as I remember it. I applied for the python-sig mailing list a
bit later. When I finally noticed on IRC that I had missed something in the
process, I read the wiki and realized I needed to post a Self
>> only place that I can have any dialog is this mailing list or
> >> #fedora-python. Application to the FAS group is a one time, one way
> >> thing. Application to the python-sig mailing list is a one way thing. A
> >> human on the other end must make some action to m
many months. So let me ask this in
return: what is the process once someone has done everything in [0]? The
only place that I can have any dialog is this mailing list or
#fedora-python. Application to the FAS group is a one time, one way
thing. Application to the python-sig mailing list is a one way
So let me ask this in
> return: what is the process once someone has done everything in [0]? The
> only place that I can have any dialog is this mailing list or
> #fedora-python. Application to the FAS group is a one time, one way
> thing. Application to the python-sig mailing list is
everything in [0]? The only place
that I can have any dialog is this mailing list or #fedora-python.
Application to the FAS group is a one time, one way thing. Application to
the python-sig mailing list is a one way thing. A human on the other end
must make some action to move the process forward.
Out
Hello Tim! Welcome to python-devel, and sorry for us being so quiet.
Is there anything in particular you're pinging about?
If want to access the python-sig FAS group, note that an introduction
here is just a part of the process [0]. However, that list is mostly
used to get notifications
Ping. Again.
On Thu, May 12, 2016 at 9:32 PM, Tim Orling wrote:
> Ping.
>
> On Fri, Apr 29, 2016 at 6:56 AM, Tim Orling wrote:
>
>> Greetings,
>>
>> I recently became a co-maintainer for pystatgrab [1] and am a contributor
>> to upstream [2]. I am a co-founder and co-maintainer of the meta-pyth
Hi there,
I am Ardian a student from Kosovo. I have been contributing to fedora
for quite some time as an Ambassador, I am almost done with my studies
so there is more free time, I would like to contribute in the
coding/packaging different parts of the project. Python being one of my
first and fav
Hello,
I am a member of Red Hat's Python Maintenance team and I have applied for the
FAS group as well as the mailing list.
I am interested in Python in Fedora, upstream and well, everything python
related.
Regards,
Charalampos Stratakis
___
python-d
Ping.
On Fri, Apr 29, 2016 at 6:56 AM, Tim Orling wrote:
> Greetings,
>
> I recently became a co-maintainer for pystatgrab [1] and am a contributor
> to upstream [2]. I am a co-founder and co-maintainer of the meta-python [3]
> and meta-maker [4] layers for OpenEmbedded. I am also a contributor
Greetings,
I recently became a co-maintainer for pystatgrab [1] and am a contributor
to upstream [2]. I am a co-founder and co-maintainer of the meta-python [3]
and meta-maker [4] layers for OpenEmbedded. I am also a contributor to
IronPython [5] and RobotFramework [6].
In my professional life, I
; On 28 April 2016 at 23:04, Petr Viktorin wrote:
>> I've applied to the python-sig FAS group and mailing list. According to
>> [SIG page] I also need to introduce myself, so here goes:
>>
>> Hello!
>> I'm the keeper of [PortingDB], team lead in Red Hat&
On 28 April 2016 at 23:04, Petr Viktorin wrote:
> I've applied to the python-sig FAS group and mailing list. According to
> [SIG page] I also need to introduce myself, so here goes:
>
> Hello!
> I'm the keeper of [PortingDB], team lead in Red Hat's Python Mainten
Petr Viktorin schrieb am Do., 28. Apr. 2016, 15:04:
> I've applied to the python-sig FAS group and mailing list. According to
> [SIG page] I also need to introduce myself, so here goes:
>
> Hello!
> I'm the keeper of [PortingDB], team lead in Red Hat's Pyth
I've applied to the python-sig FAS group and mailing list. According to
[SIG page] I also need to introduce myself, so here goes:
Hello!
I'm the keeper of [PortingDB], team lead in Red Hat's Python Maintenance
team, and I'm generally interested Python in Fedora. Please let me
On Tue, Jan 27, 2015 at 08:59:13AM -0500, Bohuslav Kabrda wrote:
> Packaging Python extension modules should keep working the way it
did up until F21. python-dateutil will still be the Python2 build,
python3-datetuil will still be the Python3 build. There are some
guidelines changes that I pr
ng nicely, I think it would be
>
> > > nice to get in touch with python-sig, the maintainers of
>
> > > python3-dateutil, about retiring python3-dateutil and adding a python3
>
> > > subpackage to python-dateutil. They might want to do it the other way
>
&g
ejewski-Szmek wrote:
> > > Hi,
> > >
> > > since bug #1126521 seems to be progressing nicely, I think it
> > would be
> > > nice to get in touch with python-sig, the maintainers of
> > > python3-dateutil, about retiring python3-dateutil and
Pete Travis schrieb am Mon Jan 26 2015 at 5:24:32 PM:
> On 01/26/2015 08:53 AM, Zbigniew Jędrzejewski-Szmek wrote:
> > Hi,
> >
> > since bug #1126521 seems to be progressing nicely, I think it would be
> > nice to get in touch with python-sig, the maintainers of
Hi,
it took a bit longer than expected to get the FAS group sorted [1], yet it
should be possible now to add the "group::python-sig" to existing and new
python packages [2-3].
So feel free to add packages to:
* add group::python-sig to python related packages
* add yourself to the pyth
- Original Message -
> From: "Thomas Spura"
> To: "Fedora Python SIG"
> Sent: Tuesday, 7 October, 2014 3:41:23 PM
> Subject: Re: python-sig in pkgdb2?
>
> 2014-10-07 9:10 GMT+02:00 Bohuslav Kabrda :
> > - Original Message -
> &
ates can be managed better and
>> several people have an eye on them.
>>
>> What do others think about that? Who else would be interested in
>> starting a common python-sig group in pkgdb2?
>
> I'm generally +1 for this, although I think people should still first tr
at do others think about that? Who else would be interested in
> starting a common python-sig group in pkgdb2?
I'm generally +1 for this, although I think people should still first try to
contact the primary maintainer and then patch things themselves. For example,
in python{,3}.spec, we'
On Tue, Oct 7, 2014 at 1:26 AM, Thomas Spura wrote:
>
> What do others think about that? Who else would be interested in
> starting a common python-sig group in pkgdb2?
>
I am in.
Kushal
--
CPython Core Developer
http://fedoraproject.org
http://
On 10/07/2014 01:13 PM, Toshio Kuratomi wrote:
> I've stepped back from packaging for the most part but I think this is a
> great idea. When I was active I'd often find something to cleanup in
> python packaging for each release (pil => pillow; removing
> python-setupto
I've stepped back from packaging for the most part but I think this is a
great idea. When I was active I'd often find something to cleanup in
python packaging for each release (pil => pillow; removing
python-setuptools-devel). A python-sig group would definitely help with
future
an eye on them.
>
> What do others think about that? Who else would be interested in
> starting a common python-sig group in pkgdb2?
>
I am.
> Greetings,
> Tom
>
> [1]
https://lists.fedoraproject.org/pipermail/devel-announce/2014-October/001445.html
> ___
need for it (or ipython
introduces a new dependency). Such packages are good candidates to be
maintained by a group of people, so updates can be managed better and
several people have an eye on them.
What do others think about that? Who else would be interested in
starting a common python-sig group
Am 18.03.2010 15:39, schrieb Stanley A. Klein:
> I think the issue of Python distutils/setuptools is important. I posted a
> note to the Python Distutils SIG asking if there was any way I could do an
> RPN package (using bdist_rpm) with results going to my usual rpmbuild
> directory tree instead o
March 19, 2010 8:00 am, Toshio Kuratomi and
Gael Varoquaux wrote:
>
> Message: 3
> Date: Thu, 18 Mar 2010 15:17:23 -0400
> From: Toshio Kuratomi
> Subject: Re: Python SIG
> To: Fedora Python SIG
>
> On Thu, Mar 18, 2010 at 03:11:15PM +, Jos? Matos wrote:
>>
On Thu, 2010-03-18 at 15:11 +, José Matos wrote:
> On Wednesday 17 March 2010 19:36:35 David Malcolm wrote:
> > How about this:
> > "A SIG for people who are interested in Python on Fedora. This includes
> > packaging and optimizing the various Python 2 and Python 3 runtimes
> > (CPython, Jytho
52 matches
Mail list logo
