Thanks for writing this report, Nga.
I’m a bit surprised that there are 6 committers who are not PMC members. I
thought that after graduation, anyone not in the initial PMC (approved by the
motion to graduate the project) has no status.
> On May 6, 2024, at 2:57 PM, Nga Chung wrote:
>
> Hi
Something to consider is keeping the site and the code in the same repo, which
is what Calcite does.
Calcite builds a site (hosted on Apache rather than RTD) based on a Git branch
(called “site”) of our main repo. This allows us to update the site without
making a release.
But we sometimes
ndation/board/reporting#how
>
> On 2024/03/20 00:33:14 Julian Hyde wrote:
> > I know I need to do something to register the release. As an ASF member I
> > know that I have the necessary karma to do this thing, and I’m happy to
> > help. But I don’t recall what exactly I need
I know I need to do something to register the release. As an ASF member I know
that I have the necessary karma to do this thing, and I’m happy to help. But I
don’t recall what exactly I need to do. As RM, I think you should have received
an email from Reporter?
Julian
> On Mar 19, 2024, at
Sounds to me as if the ‘hiccup’ is just a bug and can be addressed by
documenting it in the release notes (i.e. without needing a new RC). The bigger
issue addressed by the release is the need to remove all category X
dependencies. That said, I’m not the RM so it’s not my call.
+1 (binding)
personally in favor of the two-tier solution as I think it would be
> > more suitable for
> > > growing our community. As Julian said it's a lower barrier to entry.
> > >
> > > On 2024/01/16 22:53:38 Julian Hyde wrote:
> > > > In favor of one tier (every
>>
>> That makes a lot of sense as a better alternative to the whole nomination
>> process.
>>
>> On 2024/01/11 23:56:13 Julian Hyde wrote:
>>> I don't think the process needs to be very formal (e.g. included in
>>> the bylaws) or agreed
Since Thomas raises the point, I think it would be a bad idea to “discuss PMC
process” at the meeting.
Riley started a thread on dev@ on an important topic — how to nominate and vote
for committers and PMC members. We can agree on a process if people respond to
the thread and we get to
I don't think the process needs to be very formal (e.g. included in
the bylaws) or agreed before graduation. But it does need to be an
organizational habit. This discussion thread, if it reaches consensus,
could be all the process we need.
KVRocks' template email starts 'I nominate...'. I think
I don’t have a good answer to that. In the java world, we use maven or gradle,
and there may be plugins to assert that the license is acceptable for an ASF
project (and remains acceptable each time the dependency is upgrade), but I’m
not fully aware of those plugins. For other languages my
ected to join the Apache SDAP PMC upon
> graduation:
>
> - Nga Thien Chung (chair)
> - Edward M Armstrong
> - Thomas Cram
> - Frank Greguska
> - Thomas Huang
> - Julian Hyde
> - Joseph C. Jacob
> - Jason Kang
> - Riley Kuttruff
> - Thomas G Loubrieu
> -
Thank you, Nga!
> On Dec 19, 2023, at 3:41 PM, Nga Chung wrote:
>
> Hi all,
>
> Meeting minutes from today's meeting can be found here:
> https://cwiki.apache.org/confluence/display/SDAP/2023-12-19+SDAP+Monthly+Meeting
>
> Thanks,
> Nga
>
> On Mon, Dec 18, 2023 at 9:13 PM Nga Chung wrote:
r until a successor is appointed; and be it
> further
>
> RESOLVED, that the Apache SDAP Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator SDAP
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apach
e!
>
> On 2023/12/01 22:07:09 Julian Hyde wrote:
>> I checked SDAP’s roster page on Whimsy [1], and there are 4 red items that
>> need to be done before graduation. I don’t know which of you are allowed to
>> see this page, so I’ve pasted them below. Let’s start workin
ience Data Analytics Platform"' with no results, though
> I'm not certain if that's adequate. I also did searched: Canada trademarks,
> WIPO and EUIPO with some live matches for SDAP, but none that seem to
> conflict with us.
>
> [1] https://www.apache.org/foundation/marks/naming.
ion Software
> Instrument Software and Science Data Systems
> Jet Propulsion Laboratory, California Institute of Technology
> (818) 354-2747
>
>
>
>
> On 12/1/23, 2:08 PM, "Julian Hyde" <mailto:jhyde.apa...@gmail.com> <mailto:jhyde.apa...@gmail.
I checked SDAP’s roster page on Whimsy [1], and there are 4 red items that
need to be done before graduation. I don’t know which of you are allowed to see
this page, so I’ve pasted them below. Let’s start working on these.
Licensing
* No Software Grant and No IP Clearance Filed
* No Release
+1 (binding)
Downloaded; checked hashes; checked LICENSE, NOTICE, DISCLAIMER; verified that
chardet has gone.
Julian
Stepheny, I assume you’re ‘+1’ but you should vote explicitly.
> On Nov 28, 2023, at 10:20 AM, Riley Kuttruff wrote:
>
> I verified:
> - Release commits
> - Artifacts
Thank you for this summary. If it’s not a policy to send a summary after every
monthly meeting, could we make it so?
As you know, the project should not be making decisions at meetings.
Discussions are fine, but sometimes there is no clear line between discussions
and decisions. So, a good
The link says it very well. The main job of the Chair (aka VP) is to
communicate with the board. They don’t have any greater power than any other
PMC member, although they “hold the microphone” and so can help start and shape
the discussions.
Typically one, two or three candidates volunteer,
[
https://issues.apache.org/jira/browse/SDAP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789579#comment-17789579
]
Julian Hyde commented on SDAP-491:
--
Good points. Thank you, [~curcuru]!
> Adopt an official logo for S
[
https://issues.apache.org/jira/browse/SDAP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788874#comment-17788874
]
Julian Hyde commented on SDAP-491:
--
[~rkk], No, the project vote just sets broad direction
[
https://issues.apache.org/jira/browse/SDAP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788871#comment-17788871
]
Julian Hyde commented on SDAP-491:
--
The vote is currently under way, but both of the finalists use
I vote for logo B.
Julian
> On Nov 22, 2023, at 11:09 AM, Joseph C. Jacob wrote:
>
> I vote for logo B.
>
> Thanks,
>
> Joe
>
> On 2023/11/22 18:25:17 Riley Kuttruff wrote:
>> Hi everyone,
>>
>> After the discussion, we have 2 clear front-runners: 5 and 3.
>>
>> So now we will start the
98H
>>>
>>> From: Thomas Huang
>>> Date: Tuesday, November 21, 2023 at 10:16 AM
>>> To: dev@sdap.apache.org
>>> Subject: [EXTERNAL] Re: [DISCUSS] SDAP Logo Candidates
>>> Here are my votes: 5 (C) is my first choice - I like the NASA worm red
ates with the idea of holding a vote to ratify the favorite. We can
> replace that with this kind of vote if it's easier; I went for a two-step
> process as I was under the impression formal votes were more yes/no than
> multiple-option.
>
>> On 2023/11/21 17:21:37 Julian Hyde wr
My top choices are 4 and 5.
I suggest that the VOTE thread is a “runoff” between the 2 logos that occur
most often in people’s favorites. (Or 3 if there are no 2 clear leaders.)
> On Nov 21, 2023, at 9:20 AM, Riley Kuttruff wrote:
>
> Hi everyone,
>
> Here are the current candidates for
ense.us/v3/__https://aka.ms/o0ukef__;!!PvBDto6Hs4WbVuu7!PY1u1SmML9_ZeRBpM2ZJx5Hji6xeo8xc2gayPV-bfC7d2stEnELCQqRaMp1UjP_wfwkBoRdwcdg4SuiqwJ3pxAn-YI_Cl7MiAUvu1oPhwuyQHXY$
>
> <https://urldefense.us/v3/__https://aka.ms/o0ukef__;!!PvBDto6Hs4WbVuu7!PY1u1SmML9_ZeRBpM2ZJx5Hji6xeo8xc
d with Apache TM:
> https://issues.apache.org/jira/secure/attachment/13064496/SDAP%20logo%20bold%20Apache%20TM.png
>
> Thanks,
> Nga
>
> On Thu, Nov 16, 2023 at 4:25 PM Julian Hyde wrote:
>>
>> Thanks for the slack invite, Riley.
>>
>> I see the log
, by including the logo on the first slide of a
presentation, you've immediately addressed a number of branding
issues.
Julian
On Thu, Nov 16, 2023 at 3:43 PM Riley Kuttruff wrote:
>
> I added you to the channel.
>
> On 2023/11/16 23:39:53 Julian Hyde wrote:
> > Curious fact. I have ne
Curious fact. I have never seen the Slack channel. And I have never
been able to discover its URL.
On Thu, Nov 16, 2023 at 3:37 PM Huang, Thomas (US 398F)
wrote:
>
> I also posted my logo design on the Apache #sdap slack channel.
>
> Thanks
>
> Thomas.
>
>
> Thomas Huang
> Group Supervisor,
ASF email strips images. Because you know what happens if you allow
posting of images to public archived mailing lists.
Suggest you upload to a site like https://pastebin.com/ and post a URL.
On Thu, Nov 16, 2023 at 3:35 PM Huang, Thomas (US 398F)
wrote:
>
> Strange. My JPL email was marked as
I am genuinely puzzled why SDAP has not started talking about
graduation on the dev list. Graduation in the ASF basically consists
of a discussion followed by a vote on the dev list, and a discussion
followed by a vote on the Incubator list. There are some housekeeping
tasks in the middle, and
I signed off. Thanks for the reminder.
I also asked Google Bard to design a logo. (If someone can feed this into a
graphics GenAI I think we’re done!)
$ generate a logo for apache sdap
> Sure, here is a logo for Apache SDAP:
>
> The logo is designed to be simple and easy to understand. It is
>
, at 12:46 PM, Huang, Thomas (US 398F) <
thomas.hu...@jpl.nasa.gov> wrote:
Hi @Julian Hyde
We have new data transformation solutions approved for open-source release
that we are considering adding to the Apache SDAP umbrella. Currently,
Caltech has the copyright to the source code. It’s been
for the confusion.
>
> Stepheny
>
>> On 2023/11/01 21:21:56 Stepheny Perez wrote:
>> Hello everyone,
>>
>> The vote for 1.2.0-rc1 has passed with count of +3.
>>
>> Binding +1 votes:
>> - Riley Kuttruff
>> - Nga Chung
>> - Julian Hyde
+1 (binding)
Downloaded, checked signatures, LICENSE, NOTICE, DISCLAIMER; compared
against git tags; ran docker build; checked licenses.
Note: I followed the instructions at
https://incubator-sdap-nexus.readthedocs.io/en/latest/build.html.
Copy-pasting twenty or so shell commands to perform a
[
https://issues.apache.org/jira/browse/SDAP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767308#comment-17767308
]
Julian Hyde commented on SDAP-491:
--
The most important thing is to reach consensus, and that's done
[
https://issues.apache.org/jira/browse/SDAP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767245#comment-17767245
]
Julian Hyde commented on SDAP-491:
--
I would expect to see a discussion or vote on the dev list about logo
[
https://issues.apache.org/jira/browse/SDAP-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17757144#comment-17757144
]
Julian Hyde commented on SDAP-483:
--
I saw you merged [PR
85|https://github.com/apache/incubator-sdap
[
https://issues.apache.org/jira/browse/SDAP-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756587#comment-17756587
]
Julian Hyde commented on SDAP-483:
--
Thanks. I've added those 3 to the list. It's best that we have
[
https://issues.apache.org/jira/browse/SDAP-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated SDAP-483:
-
Issue Type: Task (was: Bug)
> Configure GitHub to automatically convert Jira references to hyperli
[
https://issues.apache.org/jira/browse/SDAP-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756582#comment-17756582
]
Julian Hyde commented on SDAP-483:
--
I have logged INFRA-24912. [~rkk], please check that I have
Julian Hyde created SDAP-483:
Summary: Configure GitHub to automatically convert Jira references
to hyperlinks
Key: SDAP-483
URL: https://issues.apache.org/jira/browse/SDAP-483
Project: Apache Science
I have signed off the report. Thank you for submitting it in a timely manner.
These were my comments on the report:
> I think SDAP is ready to graduate. In my opinion, a third
> release is not a necessary condition for graduation. The
> low participation in the graduation discussion is a little
If we are distributing components from outside the project, our
obligation is to comply with the licensing requirements of their
authors/copyright holders.
It seems that NASA imposes no requirements, other than that we do not
imply endorsement by NASA. So we're good.
The NOTICE file exists
/display/INCUBATOR/June2023#sdap
>>
>> Thanks,
>> Nga
>>
>> On Tue, Jun 6, 2023 at 10:43 AM Julian Hyde wrote:
>>>
>>> It’s possible that June isn’t when SDAP is scheduled to report, and equally
>>> possible that there is an error in t
It’s possible that June isn’t when SDAP is scheduled to report, and equally
possible that there is an error in the scripts that generate that page.
In any case, you can file a report. You should add the boilerplate by hand
(perhaps copying from the previous SDAP report).
When you’ve added the
Done. I also registered release 1.0.0 (incubating) for 2023-01-18. I
used the URL https://reporter.apache.org/addrelease.html?incubator-sdap.
On Tue, May 16, 2023 at 2:23 PM Nga Chung wrote:
>
> Hi Julian (or anyone else who has permission),
>
> Can you please help us register the SDAP 1.1.0
ared to go to both.
>
> On 2023/05/01 23:39:37 Julian Hyde wrote:
>> (I am a mentor of SDAP but was too late to vote in the thread on dev@sdap.)
>>
>> +1 (binding)
>>
>> Checked signatures/hashes, compared with git, checked NOTICE, LICENSE.txt,
>> DISCLAIMER-WIP
(I am a mentor of SDAP but was too late to vote in the thread on dev@sdap.)
+1 (binding)
Checked signatures/hashes, compared with git, checked NOTICE, LICENSE.txt,
DISCLAIMER-WIP; built Collection Manager and Granule Infester using Docker,
following the instructions in README.
Notes:
* You
Sorry I missed this vote. As a mentor, I consider it my duty to vote on all
podling releases, but my email inbox has been full for the past few days, so I
missed this one.
I saw the vote on general@ and I’ll vote shortly.
There were one or two votes that were a simple ‘+1’. I would ask those
; Thanks,
> Nga
>
> On Mon, Jan 30, 2023 at 10:23 PM Nga Chung wrote:
>
>> Thanks Julian. The report has been updated accordingly.
>>
>> Best,
>> Nga
>>
>>
>>
>> On Mon, Jan 30, 2023 at 7:08 PM Julian Hyde
>> wrote:
>&g
Thanks for completing this in good time. I will sign off now, but feel free to
make any of the following edits:
* I don’t think "Provide promotional materials (news article, video tutorials,
etc.)” is a blocker to graduation.
* I’d remove the lists of completed, new/updated issues in ‘How has
do to get to graduation. The second
release will be much easier than the first.
Julian
On Wed, Jan 18, 2023 at 3:16 PM Julian Hyde wrote:
>
> The downloads page shows up on both sdap.apache.org and
> sdap.incubator.apache.org for me. That you saw some inconsistency is
> not surprisin
et's release on Friday (2023-01-20) to give
> us a little time to get everything in order.
>
> By the way, when adding the downloads page, I noticed it shows on
> sdap.apache.org but not sdap.incubator.apache.org. Is that expected?
>
> -Riley
>
> On 2023/01/18 23:06:46
ter the release with the link you provided, but I am
> unable to do anything on that page. I just see a message saying "It doesn't
> look like you are on any PMCs"
>
> -Riley
>
> On 2023/01/18 02:44:35 Julian Hyde wrote:
>> Congratulations to SDAP on gettin
ISCUSS thread here [1] so maybe it was missed by
> > folks.
> >
> > Thanks for your guidance regarding the meeting format. We'll make sure to
> > follow and send out a summary.
> >
> > Best,
> > Nga
> >
> > [1] https://lists.apache.org
Thanks for the heads up. Was this announced earlier?
In Apache we need to be inclusive of people who prefer asynchronous
communication (in other time zones, for example) so be sure to not
make any decisions at the meeting, and send a summary of the meeting
to this list. A good pattern is to start
Downloaded artifacts, checked signatures and hashes, checked NOTICE
(noted updated year), LICENSE, DISCLAIMER-WIP, file headers.
I compared each tarball with the contents of git as of the commit
described in the voe email. I noted that gradle-wrapper.jar is no
longer in apache-sdap-nexusproto
[
https://issues.apache.org/jira/browse/SDAP-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17654319#comment-17654319
]
Julian Hyde commented on SDAP-424:
--
We had the same problem in CALCITE-4575. The solution was to exclude
gt;
> - Frank
>
> On Tue, Jan 3, 2023 at 2:35 PM Julian Hyde wrote:
>
> > Can someone explain why SDAP has 3 separate GitHub repositories rather
> > than one?
> >
> > It's not my place to suggest changes. But if the separate repositories
> > are causing more pa
Can someone explain why SDAP has 3 separate GitHub repositories rather than one?
It's not my place to suggest changes. But if the separate repositories
are causing more pain than joy, it might be worth reconsidering.
(Several times I have typed in
https://github.com/apache/incubator-sdap/ and
[
https://issues.apache.org/jira/browse/SDAP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17654196#comment-17654196
]
Julian Hyde commented on SDAP-422:
--
A more conventional structure would be to use the base name of the tar
n general@, given that it's coming up on a holiday
> weekend.
>
> On 2022/12/23 17:44:44 Julian Hyde wrote:
> > Did you see my remark about tar file structure in
> > https://lists.apache.org/thread/8h5fw3cpx81w7nmm385hlx261sbo9m0n ?
> >
> > On Thu, Dec 22, 2022 at
/23 00:12:17 Julian Hyde wrote:
> > Yes. I didn’t want to use the word “issue” twice in one sentence.
> >
> > Julian
> >
> > > On Dec 22, 2022, at 15:51, Riley Kuttruff wrote:
> > >
> > > Thanks Julian, I'll try to get the thread started by EOD.
>
Jira?
>
> Thanks,
> Riley
>
>> On 2022/12/22 23:37:44 Julian Hyde wrote:
>> PS Don’t make a new RC. The IPMC will vote on the exact same artifacts.
>>
>> Julian
>>
>>>> On Dec 22, 2022, at 15:20, Julian Hyde wrote:
>>>
>>> Nex
seriously.
Julian
> On Dec 22, 2022, at 10:15, Riley Kuttruff wrote:
>
> Julian,
>
> Are PPMC votes implicitly binding or does it need to be explicitly stated?
>
> Riley
>
>> On 2022/12/22 17:27:09 Julian Hyde wrote:
>> Thomas, (and others on this thread), it
PS Don’t make a new RC. The IPMC will vote on the exact same artifacts.
Julian
> On Dec 22, 2022, at 15:20, Julian Hyde wrote:
>
> Next step is to carry out a vote on the gene...@incubator.apache.org list.
>
> This may seem like unnecessary bureaucracy; for which I apolog
>>> to take over as release manager because I will be away 12/16/22 - 1/16/23.
>>>
>>> I captured initial release instructions here
>>> https://github.com/ngachung/incubator-sdap-nexus/blob/SDAP-414/docs/release.rst
>>>
>>> Thanks,
>>> Nga
&g
Thomas, (and others on this thread), it is helpful if you provide rationale for
your vote. What steps did you take to verify the release? Did you encounter any
matters of concern?
Julian
> On Dec 21, 2022, at 3:05 PM, Thomas G Loubrieu wrote:
>
> +1
>
>> On 2022/12/20 16
Riley, as interim release manager, can you please send a [CANCEL] email. Every
vote thread needs to be finished.
Julian
> On Dec 21, 2022, at 3:04 PM, Thomas G Loubrieu wrote:
>
> +1
>
>> On 2022/12/08 22:40:48 Riley Kuttruff wrote:
>> All release files have been verified, built and
2.nc is a publicly
> accessible NASA file. Would you advise us to remove these?
>
> Thanks,
> Stepheny
>
>
>> On 2022/12/20 00:17:00 Julian Hyde wrote:
>> The vote email is much improved; thank you!
>>
>> I downloaded the artifacts using svn, checked signatur
The vote email is much improved; thank you!
I downloaded the artifacts using svn, checked signatures (.asc files),
LICENSE, NOTICE, DISCLAIMER, VERSION.txt, file headers; I verified
that the contents of each tar file matches the corresponding git
commit. Checked for binary files.
I see that
:
>
> Not sure if it's appropriate to reply here, but is it possible to designate
> an interim release manager to kick off the next vote as Nga is out of the
> country and will be until 1/16?
>
> On 2022/12/18 06:31:15 Julian Hyde wrote:
> > I downloaded the artifacts using svn,
I downloaded the artifacts using svn, checked signatures (.asc files),
LICENSE, NOTICE, DISCLAIMER, file headers; I verified that the
contents of apache-sdap-nexus-1.0.0-src.tar.gz are equal to the
contents of the git commit tagged with 1.0.0-rc2. Checked for binary
files. That all looks good.
By the way, I wouldn't create a new RC for the vote. Just vote on the
RC1 you already have. We know we'll need to iterate through a few RCs
before we get a good one.
On Wed, Dec 7, 2022 at 1:05 AM Julian Hyde wrote:
>
> Hey, that looks pretty good! In fact it looks a lot like an Apache r
pache-sdap-nexus-1.0.0-src.tar.gz >
> > apache-sdap-nexus-1.0.0-src.tar.gz.sha512
> >
> > svn co
> > https://urldefense.us/v3/__https://dist.apache.org/repos/dist/dev/incubator/sdap__;!!PvBDto6Hs4WbVuu7!aY2tIy4CD6wRO7JlwQ9_XSOpDkqvhu8QMq2ROLe907bKV-UqYPygNoR8NjtG8upBc
A monthly meeting sounds like a good idea. It will allow project
members to get to know each other, and should help build momentum.
Monthly meetings of this kind are fairly common in Apache projects.
However, the projects need to be careful that the meeting doesn't
exclude people from the
[
https://issues.apache.org/jira/browse/SDAP-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638009#comment-17638009
]
Julian Hyde commented on SDAP-414:
--
Was this plan/decision made on any mailing list? The most recent email
[
https://issues.apache.org/jira/browse/SDAP-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637509#comment-17637509
]
Julian Hyde commented on SDAP-414:
--
How much work needs to be done to get the code and doc into shape
ulian
On Nov 9, 2022, at 3:32 PM, Nga Chung wrote:
I'm going to be the release manager for this first release. Where exactly
do we upload the 3 .tar.gz (1 per repository) to?
Thanks,
Nga
On Thu, Nov 3, 2022 at 5:12 PM Julian Hyde wrote:
Regarding testing. I recommend that the release manager cr
Regarding testing. I recommend that the release manager creates a
recipe ("HOWTO") for the steps to create a release. One of those steps
is a manual smoke test (e.g. am I able to start the server and do x,
y, and z simple operations).
Other people voting on the release can do their own smoke
I suggest doing the simplest thing. Generally the simplest thing is to
do one release from each git repository, so that you can say release
x.y.z is made from commit abcd1234, you can make the release from one
directory, and when you have CI there's only one CI job to validate
the software.
(I
> Julian,
>
> The release I was referring to in our report was 0.4.5a56 which is an alpha
> release. Would specifying this in the report make it more accurate? If not, I
> can remove that from the report altogether. Thanks for your feedback.
>
> Stepheny
>
> From: Julian Hyde
>
Thanks for writing and submitting the report, Stepheny.
I signed off and made the following comments:
> The report says that there has been a release. I dispute
> that. There is no release vote on dev@, no mention of the
> release on dev@, nothing on announce@, and no downloads page.
>
> As far
The report needs to be submitted in a few days. Is there a volunteer to write
it?
There has been some discussion about graduation this month. In the report I
would like to see a plan for how SDAP intends to graduate, and a timeline for
when that can happen.
As I have said before, I came on
Thanks to everyone who joined the discussion.
It looks to me as if the project has a healthy level of ongoing development,
and the community works together effectively on the mailing lists.
There are only two things missing:
(1) a release,
(2) for the community to say 'yes! we're ready to
I attended Stepheny's talk at ApacheCon in New Orleans last week, and
was impressed at the set of software you have all built. But also
surprised that after five years the project has still not graduated
[1].
With Trevor as the only active mentor, it seems that you could use
another mentor; I
89 matches
Mail list logo
